API searches cost the same as in the app: 1 credit per email found, 40 credits per phone number found, and 0.25 credit per email verified. Searches that find nothing are free. Your balance in the app updates in real time, and GET /account/info gives it to your code for free.
What each search costs
Email Finder: 1 credit per email found. Nothing if no email is found.
Phone Finder: 40 credits per number found (50 on legacy plans and on credit packs bought before June 18, 2026). Nothing if no number is found.
Email Verifier: 0.25 credit per verification, whether the address is valid or invalid.
A bulk search costs the same per result as single searches. Getting results with GET, checking your balance with GET /account/info and receiving webhooks are free.
Searches that fail because of a problem on Enrow's side are never charged.
Each search is done live. If you search for the same contact twice, you pay twice when a result is found. Store the results you get.
Credits are reserved, then refunded
When you send a search, Enrow takes the full cost from your balance, as if a result will be found. When the search ends without a result, these credits come back. This is why your balance can drop when a large batch starts, then go back up.
The POST response shows the reserved amount in
credits_used.The final cost is in the result:
credits_usedin the GET response of a single search,credits.costin the webhook. For a bulk search, the results show the credits charged and refunded.A bulk request needs enough credits for all its rows when you send it. If your balance is too low, the API returns an error 402 and the batch doesn't start.
Subscription credits are used first, then pay-as-you-go credits. Some responses show where the credits came from in credits.source: sub (subscription), paygo (pay-as-you-go) or mixed.
Track your balance and usage
In the app: the CREDITS block at the bottom of the left menu shows your balance, split into Subscription and Pay-as-you-go. It updates in real time, API use included.
In your code:
GET /account/inforeturns your balance in thecreditsfield. Call it before a large batch, or at regular times.In Analytics: go to Analytics in the left menu and set the Origin filter to API. You see your API searches, their success rate and the credits used over the period you choose. Export stats downloads an Excel file with one line per day.
Get warned before you run out
Low credit balance: an alert when your balance drops below a threshold you choose. See Get an alert when your credits run low.
API calls declined: an alert when API requests fail because you don't have enough credits or your subscription is paused, at most once a week. Turn it on for email, Slack or Discord in Profile > Notifications.
Automatic top-up: Enrow buys credits for you when your balance gets low. See Set up automatic top-up.
Your credits went faster than expected
Go to Analytics, set Origin to API, and look at which days and which features used the credits.
List everything that uses your API key: your scripts, Clay, Zapier, Make, n8n, Cargo, AI assistants connected with the key. In a team, every member with API access uses the same key.
Check your code for loops that send the same contacts again. Each new search is charged again when it finds a result.
If your key may have leaked, reset it. See Find, copy or reset your API key.
If you still can't explain the usage, contact support with the dates concerned.