Guides
Credits
The API uses the same credits as the app. You only pay for results you can use.
What costs credits
| Result | Credits | Charged when |
|---|---|---|
Email found (find-contacts, any action) | 1 | you only pay for emails that work (everything else is free) |
| Email from a business search | 1 | you only pay for emails that work (everything else is free) |
| Email checked (verify) | 0.1 | you only pay when the email works (bad or unclear emails are free) |
| Company summary (deep-search) | 0.5 | you only pay when we write the report |
What is free
- Every email that does not work, that we could not confirm ("Probably works", "Not sure", "On hold"), or that we did not find.
- 30-day reuse: if your account (app or API, any key) got an answer for the same email, the same person at the same business, or the same business's summary in the last 30 days, you get it again for free. The answer shows how many rows were reused in
cached30d. - Businesses without their own website in a business search (counted, never delivered).
- Reading jobs, lists and exports,
GET /account, and webhooks. - Everything with a test key.
- Requests that fail with an error.
Holding credits
When a job starts we hold the most it can cost (maxCreditsHeld, for example 100 rows × 1 credit = 100 credits). As results come in, only emails that work are charged; when the job ends, the rest goes back at once. If you do not have enough credits for the hold, the request fails with 402 insufficient_credits and nothing starts. Send fewer rows, or get credits in the app.
GET /api/v1/account shows your credits; every job shows creditsCharged.
Bounces
If a "Works" email bounces, upload the bounce in the app within the guarantee period and you get the credit back (same rule as in the app).