Apollo.Io API

What authentication does the Apollo.io API use?

Apollo uses API key authentication via the x-api-key header. Generate the key from your Apollo workspace settings; it is tied to a workspace user and inherits that user's permissions. Through Jentic the key is stored encrypted in the vault and injected at call time, so it never enters the agent's prompt.

Can I bulk-enrich a list of contacts in one call?

Yes. POST /people/bulk_match takes an array of person identifiers and returns enriched records in a single response, and POST /organizations/bulk_enrich does the same for companies. Use these instead of looping the single-match endpoint when you have more than a handful of records to process.

What are the rate limits for the Apollo API?

Limits are not declared in the OpenAPI spec and depend on your Apollo plan and add-ons. The platform applies per-minute and per-day caps that surface as 429 responses; bulk endpoints are usually the most cost-effective way to stay inside the limits.

How do I enrich a person's email through Jentic?

Run pip install jentic, then search Jentic for 'enrich a person', load the schema for POST /people/match, and execute it with the person's name and company domain. Jentic injects the x-api-key from your stored Apollo credentials. Run it through Jentic One, the self-hosted execution layer.

Does the API cover Apollo's email sequences?

The contact and account endpoints let you create and update CRM records that feed sequences, but starting and stopping a sequence itself is handled inside Apollo. For trigger-based outreach, combine the enrichment, contact creation, and search endpoints with sequence enrolment performed in the Apollo UI.

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

Yes. Because you run Jentic One yourself, your own rules decide which Apollo operations and credentials the agent can use. Apollo takes its search and match targets in the request body rather than the URL path, so you scope the agent by operation, for example allowing it to enrich a person via POST /people/match or search companies via POST /mixed_companies/search while excluding CRM writes such as creating accounts, contacts, or opportunities. Only the operations you approve are exposed to the agent, and the x-api-key stays with your instance rather than the agent's prompt.