How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Clay Search API

Search creation and pagination endpoints.

Clay Search API is one of 11 APIs that Clay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Search. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, authentication docs, and rate-limit docs.

This API exposes 6 operations across 6 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 0.

Requests are made against a single base URL, https://api.clay.com/public/v0.

6 operations 6 paths 16 schemas 2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0
Base URL
https://app.clay.com
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Clay Search API declares 1 security scheme for authenticating requests. An API key is passed in the header as clay-api-key (ClayApiKey). By default, every request must be authenticated.

  • ClayApiKey — Personal API key tied to your Clay user. Create one under Settings → Account in the Clay app.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

search 6

Search creation and pagination endpoints.

POST
/search/filters-mode
Create a search from structured filters
createFilters body → 200400401402403404429
GET
/search/filters-mode/fields
List the filter fields available for a search source type
fields 1 param → 200400401403429
POST
/search/filters-mode/{search_id}/run
Run the search iterator and return the next page of results
run 1 param body → 200400401402403404413429
POST
/search/query-mode
Create a search from a Clay search query (beta)
createQueryMode body → 200400401402403404429
GET
/search/query-mode/reference
Get the Clay search query reference (beta)
queryModeReference → 200400401403429
POST
/search/query-mode/{search_id}/run
Run the query-mode iterator and return the next page of results (beta)
runQueryMode 1 param body → 200400401402403404429

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are PublicApiCompanySearchResult (12 properties), PublicApiPersonSearchResult (6 properties), PublicApiMatchedExperience (5 properties), NextQueryModePeopleResultsResponse (5 properties). Each schema is shown below with its type and property counts.

SearchFilterField
object
4 properties 2 required
SearchFieldsResponse
object
3 properties 3 required
PublicApiMatchedExperience
object
5 properties 5 required
NextSearchResultsBody
object
1 property
SearchFieldsGuidance
object
3 properties 2 required
NextQueryModePeopleResultsResponse
object
5 properties 3 required
NextQueryModeResultsResponse
NextQueryModeCompanyResultsResponse
object
5 properties 3 required
CreateSearchResponse
object
1 property 1 required
ErrorResponse
object
1 property 1 required
CreateSearchRequest
object
2 properties 2 required
PublicApiPersonSearchResult
object
6 properties 6 required
SearchCreateExample
object
2 properties 2 required
SearchGuidanceItem
object
3 properties 2 required
NextSearchResultsResponse
object
3 properties 2 required
PublicApiCompanySearchResult
object
12 properties 12 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clay-com-search-api-openapi.yml Raw ↑

Other APIs Clay publishes across the network.

Clay HTTP API Enrichment
Clay Incoming Webhooks
Clay Outgoing Webhooks
Clay Tables
Clay Integrations
Clay Chrome Extension
Clay MCP Server
Clay Me API
Clay Routines API
Clay Tables API
Where this information came from

This is an independent, third-party profile of Clay Search API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.