01THE API
Email verifier API and email finder API for your own systems
Run finding and verification from your own code. The REST API and webhooks are included from the Scale plan upward, and the same rule applies: only verified results count against your monthly limit.
Try the checks a /v1/verify call runs, on any address.
| Check | Result | What it means |
|---|
- MX hosts
- Provider
- Receives mail
- Disposable domain
02ENDPOINTS
What the API exposes
Five endpoints cover everything the interface does.
| Endpoint | Method | What it does |
|---|---|---|
| /v1/find | POST | Resolves a work address from a full name and a company domain |
| /v1/verify | POST | Runs the full check set on one address and returns each result |
| /v1/domain-search | POST | Returns the published work addresses on a company domain |
| /v1/bulk | POST | Submits a file of rows for finding or verification and returns a job id |
| /v1/jobs/{id} | GET | Returns the state of a bulk job and a link to its results |
What a response carries
Every response is JSON and every result is self describing, so a record in your database can explain itself later.
- The address, the pattern that produced it and the confidence level
- Each check by name, with its own result rather than a single rolled up score
- The role address, disposable, free provider and typo flags
- The mail provider detected from the domain MX records
- The number of independent sources that agreed on the address
- The timestamp of the verification, in UTC
03UNDER LOAD
Built to sit inside a pipeline
An API that surprises you in production is worse than no API. These are the behaviours you can rely on.
- Authentication with a bearer token per workspace, so an agency keeps client traffic separate
- Rate limits published per plan and returned in the response headers, so you can back off before you are throttled
- Idempotency keys on every write, so a retry after a timeout never double spends your limit
- Webhooks for bulk job completion, with a signed payload and retries with backoff
- Errors that name the failing field rather than returning a generic rejection
- Every call written to the audit log with the token, the workspace and the time
04WHERE IT FITS
Three places the API earns its keep
- Verification at the point of capture. A form submission or a new CRM record is verified before it is saved, so bad addresses never enter the database.
- Re-verification on a schedule. A nightly job re-checks the records due for a re-check, and the ones that stopped passing the checks are flagged before the next campaign.
- Enrichment in your own workflow. A new account in your CRM triggers a domain search, and the contacts come back into the record without anyone opening another tool.
05PLANS
Included from Scale
| Plan | API access | Bulk rows per job | Verified results each month |
|---|---|---|---|
| Starter | Not included | 1,000 | 1,000 |
| Growth | Not included | 10,000 | 5,000 |
| Scale | REST API and webhooks | 50,000 | 20,000 |