Clay
Run Treffer lookups from a Clay table with Clay's HTTP API enrichment.
This page covers the values you need for Treffer. For the enrichment itself, follow Clay's HTTP API guide. Clay includes the HTTP API integration on selected plans only.
Configuration for every endpoint
| Method | POST |
| Headers |
X-API-Key: YOUR_API_KEY
Save it as a reusable headers account, then every column can use it.
|
| Response timeout | 120000 ms or more |
Body and endpoint URL differ per lookup. Reference your table columns with Clay's
/ tokens and wrap them in quotes: our inputs are strings,
and Clay only quotes the inserted value if you do.
Email finder
Endpoint URL: https://api.treffer.io/v1/email/finder
(no trailing slash).
{
"first_name": "/First Name",
"last_name": "/Last Name",
"domain": "/Domain"
}
Inputs: full_name, or
first_name and last_name.
Plus domain or company_name;
the domain gives the more reliable match.
Fields to return: email,
deliverability,
found,
credits_consumed.
All request and response fields are on the
email finder page.
Company profile
Endpoint URL: https://api.treffer.io/v1/companies/profile
(no trailing slash).
{
"domain": "/Domain"
}
Inputs: domain or name,
or both; the domain gives the more reliable match.
Fields to return: for example legal_name,
legal_form,
register.number,
address.city,
found,
credits_consumed.
Nested fields use dot paths. All request and response fields are on the
company profile page.
Waterfalls
A hit and a miss both return HTTP 200, and a miss costs 0 credits.
Map found into its own column and run your fallback provider
only when it is false. Trying Treffer first costs nothing when we miss.
Rate limit
Clay can throttle requests per column. Set it from our rate limits and large tables run through without a 429.