Skip to main content
The Enrow API lets you find and verify professional contact information at scale. Every request is authenticated with an API key in the 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.io

What 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.
1

POST your request

Send your search parameters. You receive a unique search ID immediately.
2

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

Use the result

The qualification field tells you if the result is valid, invalid, found, or not_found.

How do I make my first request?

Authenticate with your API key in the x-api-key header and POST a search to the relevant endpoint. The example below runs a single email search:
curl -X POST https://api.enrow.io/email/find/single \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fullname": "Dwight Schrute",
    "company_domain": "dundermifflin.com"
  }'
Response:
{
  "message": "Single search operating",
  "id": "910f3e13-b2bf-442d-ab0b-4cf44d...",
  "credits_used": 1
}
The POST is asynchronous — the 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:
SingleBulk
Batch size1Up to 5,000 (3,000 for phone)
Best forReal-time lookupsLarge-scale enrichment
WebhookFull result in payloadNotification, then GET
For bulk jobs, see Find Bulk Emails, Verify Bulk Emails, and Find Bulk Phones.

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

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