Skip to main content
This page explains how to monitor your Enrow API usage and credit consumption, and how to optimize your requests to spend fewer credits. To understand how credits are priced per endpoint, see Credits & billing.

​
How do I track my API usage?

You can track Enrow API usage in two ways: visually in the dashboard, or programmatically through the account endpoint.

​
Where can I see usage in the dashboard?

The Enrow Dashboard provides a real-time view of your usage:
  • Credits consumed over time
  • Breakdown by endpoint
  • Success and failure rates
  • Remaining credits

​
How do I check usage with the API?

Query the account endpoint to check usage programmatically. Authenticate the request with your API key in the x-api-key header — no body payload is needed: 
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 credits value is your remaining balance, and webhooks lists the URLs registered on your account. See the Account info reference for the full response schema.

​
How do I optimize my API usage?

To reduce credit consumption and stay within your rate limits, batch your requests with bulk endpoints, receive results with webhooks instead of polling, and cache results you have already retrieved.
Instead of making many single requests, batch them (up to 5,000 entries per email bulk request, 3,000 per phone bulk request):
// ❌ 100 separate requests
for (const contact of contacts) {
  await findEmail(contact);
}

// ✅ 1 bulk request
await findEmailsBulk(contacts);
See Find Bulk Emails and Find Bulk Phones for batch operations.
Polling wastes credits and rate limit quota. Use webhooks to receive results automatically:
{
  "fullname": "John Doe",
  "company_domain": "example.com",
  "settings": {
    "webhook": "https://your-app.com/webhook"
  }
}
Learn how delivery works in How webhooks work.
Store results to avoid redundant API calls for the same contact.

​
FAQ

No. Querying the Account info endpoint returns your remaining credits and registered webhooks without consuming any credits.
Credits are consumed per the rules in Credits & billing. When a request fails before processing — for example a 402 Insufficient credits response — no credits are deducted. See Error handling and Status codes for the response formats.
Batch your requests with bulk endpoints and use webhooks instead of polling for results. Both reduce the number of calls you make. See Rate limits for the current request limits.

​
Next steps

Credits & billing

See how credits are consumed for each endpoint.

Account info

Retrieve your credit balance and registered webhooks.

Webhooks

Receive results automatically instead of polling.

Rate limits

Understand the API request limits before scaling up.