Public Api

by clay-run769514a3a236No license130 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Clay Public API — HTTP access for building services, apps, and integrations: GTM database search, structured table queries, and async routine and batch runs.

Instructions onlySoftware Development
AI-generated overview

Documents Clay's Public API for building HTTP integrations: GTM database search, table queries, and async routine and batch runs.

What it does
This skill is a reference guide to Clay's Public API, which is accessed over HTTP for building services, apps, and integrations. It outlines the API's main capabilities: searching people or companies in Clay's GTM database with advanced queries, running structured queries against Clay tables, and triggering async routine and batch runs. It also explains authentication, noting that the public API requires its own dedicated key created through the Clay CLI, and points to external developer documentation for exact endpoints, request and response shapes, pagination, and rate limits.
When to use it
Use this skill when building a service, app, or integration that calls Clay's Public API over HTTP. It is not intended for one-off agent tasks in a shell, which the skill directs toward the CLI instead.
Requirements
Requires a dedicated Clay Public API key, which is created with the Clay CLI and sent as a Bearer token to the Clay API endpoint. Network access to the Clay API and to the external developer documentation is needed. The skill ships no scripts; it is instructions only.

The Clay Public API

Beyond the CLI, Clay exposes a Public API you can develop against directly over HTTP. Reach for it when building a service, app, or integration — not for one-off agent tasks in a shell (use the cli skill for those).

What it offers

  • Search — find people or companies in Clay's GTM database with advanced queries: criteria from the fields catalog, cross-entity filters, and nested Boolean logic. See the searches skill for search behavior and the CLI equivalent. Prefer the CLI for one-off searches.
  • Tables — structured queries against Clay tables.
  • Routines / batches — async routine and batch runs.

Auth

The public API needs its own key — the credential from clay login is not scoped for it. Issue a dedicated public-API key with the CLI:

bash
clay api-keys create --name "<name>"   # → { ..., "apiKey": "<secret>" }

CLI-created keys are always scoped to the public API. The apiKey secret is returned only once, at creation — store it immediately; it can't be retrieved later. Send it as a Bearer token against https://api.clay.com/public/v0. Manage existing keys with clay api-keys list | update | delete.

Reference

Full developer documentation — Public API reference, CLI reference, concepts, and the OpenAPI spec — lives at:

Fetch that first to get exact endpoints, request/response shapes, pagination, and rate limits before writing integration code.

Source and attribution

Source:clay-run/agent-pluginsinclay/skills/public-apiat commit769514a

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal