Enrow API

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 your Jentic One instance 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 with Jentic One, the self-hosted execution layer.

Can I limit what my agent is allowed to do with the Enrow API?

Yes. Because you run Jentic One yourself, your own rules decide which Enrow operations the agent may call, so you can grant only what a task needs, such as POST /email/find/single or POST /email/verify/single. Enrow sends the email or phone target in the request body rather than the URL, so scoping is done at the operation level: an operation like phone discovery at POST /phone/single is reachable only if you include it in the allowed set. Your Enrow API key stays in your own Jentic One instance and is injected at execution time, so it never enters the agent's prompt or context.