Using Clay as an API
Here's how you can use Clay like an API
We get the question “Does Clay have an API?” a lot. The short answer: no.
The slightly longer answer is: mostly no—but there are some things you can do that accomplish similar outcomes.
If you’re trying to do one of these things, we might be able to help:
- Send data into Clay programmatically through webhooks.
- Use third-party tools like Make or Zapier to wrap Clay's functionality.
- Access basic people and company data through our Enterprise API.
1. Webhooks (Best for sending data)
Every Clay table has a unique webhook endpoint. You can send data into a table programmatically—say from a form submission, CRM, or another app—and Clay will start processing it immediately.
After enrichments run, you can use HTTP actions to push the data back out to your system of record. This is the most API-like workflow and is ideal for automating lead flow or enrichment jobs. Click here for more information about webhooks in Clay!
2. Wrap Clay in a third-party tool (Best for light API proxying)
You can use tools like Replit or Make as a wrapper around Clay. These tools receive API requests, trigger Clay to do its thing, and return results once processing is complete.
This works if you absolutely need an endpoint, but be aware: Clay’s enrichment model means responses might take a minute or more, and you’ll need to build logic to handle that. Click for a little tutorial on how to do that.
3. Enterprise-only People & Company API (Best for basic lookups)
For Enterprise customers, Clay offers a limited but fast API for accessing its proprietary People and Company data. You can send an email or LinkedIn URL to get back basic person details, or a domain to get company info.
- It’s useful for lightweight lookups and lead enrichment.
- It doesn’t include deep enrichment like emails, phone numbers, or revenue data.