Skip to main content
Enrow uses a credit-based system, and credits are only 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. Each feature consumes credits at a different rate:
EndpointCredits
Email Finder1 per email found
Phone Finder40 per phone found (default; 50 with legacy plans)
Email Verifier0.25 per check
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.
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. 
curl https://api.enrow.io/account/info \
  -H "x-api-key: YOUR_API_KEY"
Response
{
  "credits": 8500,
  "webhooks": ["https://your-app.com/webhooks/enrow"]
}
The response contains your balance and registered webhooks:
FieldDescription
creditsYour current credits balance
webhooksArray of your registered webhook URLs
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?

From the Billing page in the app, you can configure three options that keep your account topped up and alert you before credits run out:
Automatically renew your plan when it expires. Set the credit amount to renew in the input field next to the toggle.
Automatically purchase additional pay-as-you-go credits when your balance runs low. Set the credit amount to top up in the input field next to the toggle.
Receive an email alert when your credit balance drops below a threshold. Set the credit amount threshold in the input field next to the toggle.

​
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: 
{
  "reason": "Insufficient credits",
  "success": false
}
Bulk endpoints return { "message": "..." } instead. For the full list of status codes and response shapes, see Status codes and Error handling.
To avoid interruptions, enable Auto Top-Up or Low Balance Alert from the Billing page.

​
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 through Auto Top-Up.

​
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.
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.