Enrow API

Name: Enrow API
Brand: Enrow API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey13 EndpointsREST

For Agents

Find professional emails, verify deliverability, and discover phone numbers for B2B contacts via single or bulk operations.

Install Jentic One Beta

Connect the Enrow API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Enrow API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Enrow API.

Find a single professional email address from a person's name and company domain

Submit a bulk email-finding job and retrieve the results when ready

Verify whether a single email address is deliverable before outreach

GET STARTED

Start building with Enrow API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Enrow API, keeping it validated and agent-ready. Enrow provides email finding, email verification, and phone number discovery for B2B prospecting workflows. The API exposes single and bulk variants for each capability — find a professional email, verify deliverability, and discover phone numbers — plus an account info endpoint to monitor remaining credits. Both POST (start a job) and GET (retrieve a job) variants exist for each capability so integrations can submit asynchronously and poll for results.

Use Cases

Patterns agents use Enrow API for, with concrete tasks.

★ Outbound Prospect List Enrichment

Sales operations teams take a list of LinkedIn-derived contacts and run them through POST /email/find/bulk and POST /email/verify/bulk to attach verified, deliverable emails before importing into a sequencing tool. The bulk endpoints return a job identifier that the integration polls via the matching GET endpoint until the job is complete. Replaces multi-tool workflows that previously required separate finder and verifier vendors.

Submit POST /email/find/bulk with a 200-row payload of (full_name, company_domain), then poll GET /email/find/bulk with the job_id until status is 'done' and download the results.

Real-Time Email Verification at Form Submit

Embed POST /email/verify/single into a marketing form submission flow so risky and undeliverable addresses are rejected before they reach the CRM. The single-call endpoint returns within sub-second latency, suitable for synchronous validation. Keeps the database clean and protects the sender domain.

Call POST /email/verify/single for the submitted email and reject the form if the response is not 'deliverable'.

Phone Discovery for Sales Outreach

Sales reps run a list of high-priority accounts through POST /phone/bulk to attach phone numbers for cold-calling outreach. The bulk job returns a downloadable result set when complete, and POST /phone/single covers ad-hoc, in-the-moment lookups during research. Useful for SDRs who blend multi-channel outreach.

Submit POST /phone/bulk with a list of 50 prospects and poll GET /phone/bulk until the job completes.

AI Agent Prospect Enrichment Through Jentic

An AI sales agent uses Jentic to discover Enrow operations by intent and chains email finding, verification, and phone lookup into a single qualification pipeline. The Enrow x-api-key value stays in the Jentic vault and never enters the agent's prompt context. The agent submits bulk jobs and polls for completion without bespoke wiring.

Search Jentic for 'find a professional email at a company', load POST /email/find/single, and execute it for the captured contact.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for enrow api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/email/find/single

Find a single professional email

POST

/email/find/bulk

Submit a bulk email-finder job

GET

/email/find/bulk

Retrieve results for a bulk email-finder job

POST

/email/verify/single

Verify a single email address

POST

/email/verify/bulk

Submit a bulk email-verification job

POST

/phone/single

Discover a single phone number

POST

/phone/bulk

Submit a bulk phone-finder job

GET

/account/info

Read account info and remaining credit

POST

/email/find/single

Find a single professional email

POST

/email/find/bulk

Submit a bulk email-finder job

GET

/email/find/bulk

Retrieve results for a bulk email-finder job

POST

/email/verify/single

Verify a single email address

POST

/email/verify/bulk

Submit a bulk email-verification job

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Enrow API keys are stored encrypted in the Jentic vault (MAXsystem). Agents call /email/find/single, /email/verify/bulk, and /phone/single through scoped tokens — the x-api-key header value is never visible to the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'find a professional email at a company') and receive the matching Enrow operation with its input schema, so the agent calls POST /email/find/single without parsing developer documentation.

Time to first call

Direct Enrow integration: 1-2 days to wire up auth, the submit-then-poll pattern across bulk endpoints, and error handling. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using Enrow API through Jentic.

Why is there no official OpenAPI spec for Enrow API?

Enrow does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Enrow API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Enrow API use?

The Enrow API uses an API key passed in the x-api-key header on every request. Through Jentic, the key is stored in the vault (MAXsystem) and injected at execution time so it never enters the agent context.

Can I run bulk email-finding jobs with the Enrow API?

Yes. Submit a job with POST /email/find/bulk and poll GET /email/find/bulk with the returned job_id until the status is complete. The same submit-then-poll pattern applies to bulk verification and phone discovery.

How do I verify an email address in real time?

Call POST /email/verify/single with the address. The endpoint returns a deliverability status synchronously, so you can use it inside form-submit flows to reject undeliverable addresses before writing to the CRM.

What are the rate limits for the Enrow API?

The Enrow API uses credit-based metering rather than per-minute rate limits. Each find, verify, or phone lookup consumes credits from the account balance — call GET /account/info to check the remaining quota.

How do I find a professional email through Jentic?

Search Jentic for 'find a professional email at a company', load POST /email/find/single, and execute it with the contact's full name and the company domain. Get started at https://app.jentic.com/sign-up.

Enrow API

Connect the Enrow API to your agent

Capabilities

Start building with Enrow API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs