Skip to main content
Enrow uses a credit-based system, and credits are consumed when a result is found or a check is performed. This page explains how credits are charged for each endpoint, how to check your balance, how to manage billing settings, and what happens when credits run out.

How do credits work?

Credits are only consumed when the API returns a result or completes a check: failed lookups that find nothing do not cost credits, with two exceptions for the Email Finder (see below). Each feature consumes credits at a different rate:
Credits are charged the same way for single and bulk operations — per individual result. Running a bulk email search of 1,000 names costs the same per found email as 1,000 single searches.
Two exceptions for the Email Finder: an account whose success rate stays abnormally low pays, after a warning, 0.25 credit per search without a result, and a search from a LinkedIn profile URL costs 0.25 credit when no email is found. See the FAQ below.
Every request that consumes credits returns a credits_used field in its response, so you can track consumption per search. See Find Single Email for an example response.

How do I check my credit balance?

Query the account endpoint with your API key in the x-api-key header to retrieve your current credit balance. No body payload is needed — the account is identified from the API key.
Response
The response contains your balance and registered webhooks: For the full endpoint reference, see Account info. You can also visit your Dashboard to view usage and billing details, or check the Authentication guide for how the x-api-key header works across every endpoint.

How do I manage billing settings?

On paid plans, Billing → Settings in the app has two settings that keep your account supplied with credits and warn you before they run out:
Refills your balance automatically as soon as it drops below the credit threshold you set (at least 100 credits). Choose one of two modes:
  • Early renewal: your plan renews right away and starts a new cycle with its credits. Available only with an active subscription.
  • Pay-as-you-go top-up: a pack of pay-as-you-go credits is bought, in the top-up volume you choose.
If your balance is already below the threshold when you save, the refill happens right away.
Sends an email to the address you choose when your balance drops below a given amount. You can also post this alert in a Slack or Discord channel.

What happens when credits run out?

When your credit balance reaches zero, API requests return an HTTP 402 status. Single endpoints (email/phone find single, verify single) return:
Bulk endpoints return { "message": "..." } instead. For the full list of status codes and response shapes, see Status codes and Error handling.
To avoid interruptions, turn on Balance protection or a Credit Alert in Billing → Settings.

Which plan should I choose?

Visit enrow.io/pricing to compare plans and find the right fit for your needs. Pay-as-you-go credits can be added on top of any plan, by hand or automatically with Balance protection.

FAQ

No. Credits are only consumed when an email or phone number is found, or when a verification check is performed. A search that returns no result does not cost credits. One exception, set out in clause 8.6 of our terms of service: if fewer than 12% of an account’s Email Finder searches find an email, over at least 10,000 searches in 7 days, we warn the account in the app. If the rate is still that low 7 days later, each Email Finder search without a result costs 0.25 credit until the rate comes back up. Another exception: an Email Finder search from a LinkedIn profile URL costs 0.25 credit when no email is found. Failures caused by an incident on our side are never charged.
No. Credits are charged per individual result, so a bulk operation costs the same per found email, phone, or verification as the equivalent single requests. Bulk endpoints save on requests, not on credits.
The Email Verifier consumes 0.25 credits per check. The Email Finder consumes 1 credit per email found, and the Phone Finder consumes 40 credits per phone found (50 with legacy plans).
Requests return an HTTP 402 status. Single endpoints return { "reason": "Insufficient credits", "success": false }, while bulk endpoints return { "message": "..." }. See Error handling for details.

Next steps

Authentication

How to pass your API key in the x-api-key header.

Account info

Retrieve your credit balance and registered webhooks.

Rate limits

Understand the API request limits before scaling up.

Error handling

Handle 402 and other error responses gracefully.