x-api-key header, and every search runs asynchronously so you can process large volumes without blocking.
Base URL — All API requests go to
https://api.enrow.ioWhat can I do with the Enrow API?
The Enrow API exposes three core features, each available in both single and bulk mode:Email Finder
Find professional email addresses from a name and company domain
Email Verifier
Verify any email address with determinist catch-all verification
Phone Finder
Find direct phone numbers from a LinkedIn URL or name + company
How does the Enrow API work?
All endpoints are asynchronous and follow the same pattern: you submit a search, then collect the result via webhook or polling.Get notified or poll
Webhook (recommended): Pass a
webhook URL in settings and get the result POSTed to your server instantly. See How webhooks work.Polling: Call the GET endpoint with the search ID.How do I make my first request?
Authenticate with your API key in thex-api-key header and POST a search to the relevant endpoint. The example below runs a single email search:
- cURL
- Node.js
- Python
email and qualification are retrieved later via the GET endpoint or a webhook.
Should I use single or bulk mode?
Use single mode for real-time, one-off lookups, and bulk mode for large-scale enrichment. Every endpoint supports both:| Single | Bulk | |
|---|---|---|
| Batch size | 1 | Up to 5,000 (3,000 for phone) |
| Best for | Real-time lookups | Large-scale enrichment |
| Webhook | Full result in payload | Notification, then GET |
What makes the Enrow API different?
The Enrow API combines determinist verification with flexible result delivery, so you get accurate data without extra tooling:Catch-all verification
Determinist verification that works even on catch-all domains. No debouncer needed.
Custom fields
Pass your own
custom data with each search — it’s returned as-is in the result.Webhooks
Get results in real-time. No polling, no wasted API calls.
FAQ
How do I authenticate API requests?
How do I authenticate API requests?
Every request must include your API key in the
x-api-key header — there are no OAuth flows or bearer tokens. See Authentication for setup and examples.Why are responses asynchronous?
Why are responses asynchronous?
A POST request starts a search and returns a unique
id immediately. The email, phone, or qualification is delivered later via a webhook or by polling the matching GET endpoint with that id.How many searches can I run in one bulk request?
How many searches can I run in one bulk request?
Bulk email and email verification requests accept up to 5,000 searches, and bulk phone requests accept up to 3,000. For single requests, the batch size is 1.
How are credits consumed?
How are credits consumed?
Credits are deducted per search and the amount is returned in
credits_used. See Credits & billing for per-endpoint costs and Rate limits before scaling up.Next steps
Authentication
Set up your API key in the x-api-key header
How webhooks work
Get results in real-time, no polling needed
Credits & billing
Understand how credits are consumed per endpoint
Error handling
Status codes, qualifications, and error formats

