Clay API review
Best orchestration layer
POST <your Clay webhook URL> x-clay-webhook-auth: $TOKEN # optional # rows land in a Clay table, not in a response # 50,000 submissions per webhook, lifetime # deleting the rows does not reset the counter
Start here, because it saves an afternoon: Clay is not an API-first product and there is no conventional Clay API reference to read, and no list of Clay API endpoints to work through. Searching for one leads to Clay University, which is a learning site. What people mean by the Clay API is one of four things, and there are different prices and different limits behind each.
The first is the Clay HTTP API: a column in a Clay table that calls any external endpoint and writes the response back into a cell. That is the one most teams want, and it is a Growth plan feature at $446 a month. The second is a webhook source, which lets your systems push rows into a Clay table; that works on every plan and carries a hard cap worth knowing about. The third is bringing your own API key to a native enrichment, which is free.
None of that makes Clay a bad buy. It makes it a workbench with integration points rather than a service you call, and the Clay enrichment API people imagine is really a table that runs providers on your behalf. Judge it on that and the pricing makes sense.
The rest of the category is in the Enrichment APIs listing.
Four things people call the Clay API
These are genuinely different products with different costs, and conflating them is the usual reason a Clay evaluation goes wrong. Everything below is from Clay's own documentation at university.clay.com, read on 8 October 2026.
| Surface | Direction | What it does | What it needs |
|---|---|---|---|
| HTTP API column | Clay calls out | Sends or retrieves data from any tool or database by endpoint, even where Clay has no native integration. The response is parsed into table columns. | Growth, $446/mo |
| Webhook source | Your app calls in | Clay gives you a URL and a cURL command. Anything you POST to it becomes rows in a table. | Any plan |
| Bring your own key | Clay calls a provider | Use your own contract with a provider inside a native Clay enrichment, rather than paying Clay credits for it. | Free plan |
| Clay Sequencer and integrations | Clay calls out | Native connectors to sending tools and CRMs, configured rather than coded. | Launch, $167/mo |
Which of these you need is the whole of a Clay API integration decision, and the split that matters is between the webhook source and the HTTP API column. Pushing data into Clay is free on any plan. Having Clay reach out to something it does not natively integrate with costs $446 a month, and that is the capability most engineers assume they are buying when they read the word API. Outside the table, Clay's MCP server runs its find-and-enrich tools for a signed-in user under a credit budget the admin sets, and Clay API access, for calling Clay from your own code, is an Enterprise feature.
Clay documents webhook sources as limited to 50,000 submissions, and says plainly that the limit persists even after deleting rows. Clearing the table does not buy you more. On Enterprise you can turn on Auto-delete, also called passthrough tables, so Clay processes and discards rows and one webhook runs indefinitely. On every other plan you create a new webhook when you hit 50,000, which means anything feeding Clay continuously needs a plan for rotating the URL.
Clay API pricing, plan by plan
Clay API pricing is really Clay pricing, because nothing here is metered separately. You buy two meters, actions for the work Clay does and data credits for the data it buys on your behalf, neither is charged when an enrichment returns nothing, and the plan you are on decides which integration surfaces you can use at all.
Free
- 100 data credits a month, 1,200 a year
- Unlimited seats and tables, up to 200 rows per table
- Multi-provider waterfalls and Claygent
- Bring your own API key
Launch
- 2,500 data credits a month, 30,000 a year, unused ones roll over up to 2x
- Phone number enrichment
- Job change and other signals, unlimited Audiences search
- Send through the Clay Sequencer or an integration
Growth
- 6,000 data credits a month, 72,000 a year, unused ones roll over up to 2x
- Integrate with any HTTP API. This is the tier that unlocks it
- Auto-sync and enrich CRM, warehouse sync
- Web intent signals, webhook-driven automation
Enterprise
- Custom action and data credit volume, and Clay API access for calling Clay from your own code
- Auto-delete, so one webhook takes unlimited submissions
Each price is two meters added together on annual billing. Launch's $167 is $54 for 15,000 actions and $113 for 2,500 data credits a month, so an action is $0.0036 and a data credit $0.0452; Growth's $446 is $185 for 40,000 actions and $261 for 6,000 data credits. You are not buying cheaper units by upgrading, you are buying capabilities: HTTP API, CRM sync and warehouse sync all sit behind the Growth line. Both paid plans start a 14-day trial, and monthly billing costs about 10% more, $185 and $495.
This is the most important thing about Clay's rate card and it is easy to get wrong. Clay's pricing page says that if an enrichment returns no result, you are charged neither data credits nor actions, so a waterfall step that finds nothing costs nothing. A found contact costs an action for Clay's work plus the data credits that provider charges in Clay's marketplace, at $0.0452 a credit on annual Launch. Connect your own provider key and the data credits drop out: Clay bills the action and the provider bills you directly.
How to create a Clay API key
Below Enterprise there is no account-level Clay API key to generate, because there is no account-level API to call. Authentication depends on which surface you are using, and two of the three hand you a credential that is shown once.
Webhook source
Inbound. Clay generates the endpoint, you secure it.
- Clay gives you a URL and a ready-made cURL command to copy.
- Authentication is optional: you can add a token to the request header.
- Clay warns that you can only access the token once, so copy it before you close the dialog.
- Without a token the endpoint is open to anyone who has the URL, so treat the URL as the secret.
HTTP API column
Outbound. You supply the other service's credentials.
- The credential belongs to whatever you are calling, not to Clay.
- Clay documents the full error table, including 401 for bad credentials and 403 for missing scopes.
- A 429 from the far end means you need to set the column's own rate limit lower.
- Only available from the Growth plan.
Clay's own guidance is to use conditional run formulas so an HTTP API column only fires when the data it needs is present. The reason is that a column without a condition runs on every row in the table, including rows that were never going to return anything. Clay does not charge for an enrichment that comes back empty, but every run that does return is billed, and a condition is what keeps those runs on rows worth paying for. This is the cheapest optimization available in Clay and it is the one teams add after the first surprising invoice rather than before.
Where the Clay API documentation lives
Clay documents itself as a product to learn rather than an API to integrate, and that is a real difference from everything else in this directory. There is no OpenAPI spec, no versioned reference and no client library. What there is, is thorough.
| Surface | Where | What it answers |
|---|---|---|
| Clay Docs | university.clay.com/docs | The real documentation. HTTP API, webhooks, enrichments, signals. |
| HTTP API guide | university.clay.com/docs/http-api-integration-overview | Configuring an outbound call, rate limiting it, and the full error table. |
| Webhook guide | university.clay.com/docs/webhook-integration-guide | Inbound setup, the auth token, and the 50,000 submission cap. |
| Clay University | docs.clay.com | Courses and worked plays rather than reference. Good, but not a spec. |
| Pricing | clay.com/pricing | Which surface is on which plan, which is the question that actually blocks people. |
If you are evaluating Clay as an engineer, read the HTTP API page and the pricing page together and nothing else. Between them they answer whether Clay can do what you need and whether the plan you were going to buy allows it, and those are the only two questions that matter at the start.
Clay also ships an MCP server, and it is on the MCP page with the others in this directory.
Clay's own product walkthrough
Clay publishes this on its own channel, so it is Clay's account of Clay, not ours. It is here because a rate card cannot show you the thing moving, and a few minutes of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.
YouTube · Clay What is Clay? 4:36 · Published October 2024The platform overview, with 62,000 views and the honest caveat that it is about Clay as a growth tool rather than about the HTTP API. Clay's own channel carries nothing on the API at all, which is itself worth knowing before you plan to drive Clay from code.
Published 28 October 2024 on Clay, the channel Clay's own pages link to, and read on 13 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a Clay page.
Strengths and limits
Clay is the best workbench in this directory and the weakest API in it, and both of those are deliberate.
What it does well
- Waterfall across 150 providers without signing 150 contracts, configured by someone who cannot code.
- A free plan with unlimited seats and tables, real waterfalls and Claygent, which is unusually generous.
- Inbound webhooks on every plan, so getting data into Clay costs nothing.
- Bring your own API key, so you can use an existing provider contract instead of paying Clay data credits.
- The HTTP API column genuinely does reach anything, which is what makes Clay a router rather than a vendor.
Where it falls short
- The HTTP API column is a $446 a month feature, and that is not obvious until you are comparing plans.
- Two meters to forecast, an action for the work and data credits for the data, and the credits a lookup costs vary by provider.
- Webhook sources stop at 50,000 submissions and the counter survives deleting the rows.
- No OpenAPI spec, no client libraries, no versioned reference.
- A row's data inherits the license of whichever provider answered, which is hard to reason about in a product.
Where Clay data comes from, and what you may do with it
The question that arrives late and expensively is not how good the data is, it is who is allowed to hold it. These are the fields each one returns, the coverage it claims and the compliance it publishes.
| Provider | Fields returned | Coverage | Compliance | Redistribution |
|---|---|---|---|---|
| Clay | Work email, Personal email, Mobile phone, Firmographics, Technographics, Job postings, Job changes, Intent and news, LinkedIn profile | Global | GDPR DPA SOC 2 Type II | Not stated |
None of these states a redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first.
Two practical notes that apply to every provider on this page. A compliance badge describes the vendor, not your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And every one of these vendors runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs.
If Clay is not the answer
Four providers in the Enrichment APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.
FullEnrich
$55/moThe same multi-source waterfall as a single API call with a single credit price per result. The direct swap if you want the coverage without the workbench.
Apollo
$49/seat/moOne credit at $0.0196 for a found email, with a built-in waterfall of its own. Clay bills the same row as an action plus data credits.
LeadMagic
$99/moA published cost for every operation and credits deducted only on success. The answer when finance wants a number rather than a range.
People Data Labs
$98/moThe one to move to if the rows are going inside a product, because its terms are written for redistribution.
The full set, organized by the reason people leave, is on the Clay alternatives page.
Clay against the obvious rival
Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: Apollo vs Clay, Clay vs FullEnrich and Clay vs People Data Labs.
The same again, against the rest of the field: Clay vs HubSpot and Attio vs Clay. Every pairing in the directory is on the compare hub.
Apollo vs Clay
CompareOne key for the whole motion against a router sitting in front of 150 vendors.
Clay vs FullEnrich
CompareTwo ways to buy a waterfall: a spreadsheet you configure, or one endpoint you call.
Clay vs People Data Labs
CompareCoverage borrowed from 150 vendors against one dataset you are licensed to redistribute.
Before you build against it
Five things to settle first, each one read off Clay's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.
Who should actually buy this
Buy Clay when the person who changes the enrichment logic is not an engineer. That is the whole product. A RevOps lead adding a condition on a Thursday without filing a ticket is worth $167 a month on its own, and the waterfall across 150 providers is worth more than most teams could negotiate individually.
Do not buy Launch or Growth expecting an API. Calling Clay from your own code is Clay API access, which the pricing page lists on Enterprise only, and if your plan is to have Clay call your code, budget for Growth at $446 rather than Launch at $167. Teams that discover this after signing usually end up paying for a tier they did not plan on.
The pattern that works for most is Clay over the top rather than underneath: a cheap per-record provider handles the volume, and Clay runs on the rows that provider missed. You keep the coverage, and Clay's spend tracks the rows the cheap provider missed instead of your whole list.
Clay bills two meters. We build the filter.
Most Clay invoices are bigger than they need to be for one reason: expensive columns run on rows that were never worth enriching. Frontal puts the conditions, the dedupe and the cheap provider in front of the expensive one, inside your own workspace, and you keep it.
Worked with 300+ companies. A senior operator runs your account.
What Clay users say, in their own words
The one part of this page that is not a vendor claim. Quotes are transcribed as written and linked to the thread.
Use it as a filter, not as a bulk provider
One thing I've seen with Clay is that it feels expensive when you use it like a bulk data provider, but much more reasonable when you use it as a filter first. I rarely enrich everything. I narrow the list with cheap signals and firmographics, then only run waterfall email/phone on leads that actually look worth it. That shift alone cut my credit usage a lot, and the outreach quality went up because fewer bad leads made it through. At that point you're paying for decisions, not just data.
r/gtmengineering · January 2026 · 16 points
This is the argument the pricing section makes, arrived at from the other direction. The lever that moves a Clay bill is not the rate, it is how many rows ever reach the expensive step. Narrowing on firmographics first costs almost nothing and keeps the paid enrichments for rows worth contacting.
It also explains why a team that thinks it wants to leave Clay often does not need to. The complaint is usually the spend, and the fix is usually an ordering change rather than a migration.
Bringing your own keys is a real line item, not a hack
Working in tech sales at a large 8 figure SaaS, our current setup for the team is as follows: [...] We do still have Clay but we bring our own API keys to keep the cost down
r/gtmengineering · January 2026 · 32 points
Clay lets you connect your own provider keys instead of spending its credits on that provider. The team above keeps the workbench and pays the underlying vendors directly, which is the arrangement that makes Clay a router rather than a reseller.
Worth knowing before you compare rate cards, because it changes what you are comparing. A Clay bill with your own keys attached is a subscription for the logic; a Clay bill without them is a subscription plus a margin on every lookup. Clay's own documentation is the authority on which integrations accept your key.
14 threads read on 13 October 2026, searched by vendor name. Scores and dates are the comment's own. Nothing here is the only source for a price or a limit on this site: every figure in the tables above comes from a vendor's own page.
Clay API, answered
Is the Clay API free?
Free plan, 500 actions and 100 data credits per month. Paid use starts at $167/mo.
How much does the Clay API cost?
Clay starts at $167/mo, which works out at $0.045 per data credit. Billing is subscription, credit packs and free tier. Read from Clay's own pricing page on 19 October 2026.
What are the Clay API rate limits?
Concurrency governed by plan, not a published per-minute cap.
How do I get a Clay API key?
Optional token on a webhook source. The HTTP API column uses the other service's key. The current steps are in Clay's own documentation, which is authoritative on anything that has changed since 19 October 2026.
Does Clay have an MCP server?
Yes, at https://api.clay.com/v3/mcp. It is listed with the others on the MCP page.