Apollo.Io API
★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey43 EndpointsREST
For Agents
Enrich people and companies, search the Apollo database, and manage contacts, accounts, deals, and email sequences from your own workflow.
Use for: Enrich a person record with their work email and phone number, Search Apollo for marketing leaders at SaaS companies in EMEA, Find all open job postings for a target organisation, Create a new account record in Apollo
Not supported: Does not handle starting email sequences inside Apollo, dialer-based calling, or billing operations — use for enrichment, search, and CRM contact, account, and deal management only.
Jentic publishes the only available OpenAPI specification for Apollo.Io API, keeping it validated and agent-ready. Apollo is a sales intelligence and engagement platform that combines a B2B contact and company database with native CRM, email sequencing, and call tracking. The API exposes people and organisation enrichment, contact and account management, deal pipeline operations, email sequencing, and supporting metadata such as job postings and news articles, so revenue teams can drive prospecting and outbound from their own tooling. Authentication is by an x-api-key header tied to an Apollo workspace user.
Install Jentic One Beta
Connect the Apollo.Io API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Apollo.Io 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.
1
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 | sh2
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 instanceJentic 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 Apollo.Io API.
Enrich a person or company record with verified email, phone, and firmographic data via /people/match and /organizations/enrich
Run bulk enrichment for up to a list of records in one call via /people/bulk_match and /organizations/bulk_enrich
Search Apollo's database for prospects and accounts via /mixed_people/search and /mixed_companies/search
Create, update, and search contacts and accounts in the Apollo CRM
Manage deal pipeline stages via /opportunities and /opportunity_stages
Pull organisation job postings and news articles for trigger-based outbound
Use Cases
Patterns agents use Apollo.Io API for, with concrete tasks.
★ Outbound Lead Enrichment
Sales operations teams pipe form submissions, webinar registrants, and inbound leads through Apollo to enrich each record with verified email, phone, title, and company firmographics before pushing into the CRM. POST /people/match handles single-record enrichment in real time and POST /people/bulk_match handles batch lists of up to several hundred at a time, so outbound sequences fire against fresh data.
Call POST /people/match with the lead's name and company domain, capture the verified email, and create the contact in the CRM with that email.
Account-Based Prospecting
Account-based marketing teams identify ICP-fit accounts and the right buying-committee contacts within them. POST /mixed_companies/search filters companies by employee count, industry, and technographics, while POST /mixed_people/search returns the matching personas inside those companies, ready to enroll in a sequence.
Run POST /mixed_companies/search for SaaS companies with 200-1000 employees, then POST /mixed_people/search for VP-of-Marketing personas at those accounts.
Pipeline Hygiene Automation
Revenue operations teams automate pipeline hygiene by promoting and demoting deals based on activity. POST /opportunities/search returns deals with stale activity, PUT /accounts/{account_id} updates the parent account's stage, and POST /accounts/bulk_update reassigns segments without manual click-through. Combined, the workflow keeps the pipeline accurate without burning rep time.
Search opportunities older than 30 days with no activity via POST /opportunities/search and update each via PUT /accounts/{account_id} to demote the related account stage.
Trigger-based Outreach
Marketing teams listen for hiring spikes and news mentions on target accounts and time their outbound to those events. GET /organizations/{organization_id}/job_postings exposes hiring signals and POST /news_articles/search exposes news triggers, so a sequence can fire 'I saw you're hiring 12 SDRs' rather than a generic intro.
Call GET /organizations/{organization_id}/job_postings for each ICP account and enroll matching contacts in a hiring-trigger sequence.
AI Agent Sales Assistant
An AI sales assistant uses Jentic to call Apollo without managing the x-api-key directly. Jentic exposes the search, enrichment, and CRM operations by intent, validates inputs against the schema, and isolates the API key, so the agent only has to choose which operation matches the user's request.
Search Jentic for 'enrich a person', load the POST /people/match schema, and execute it with the lead's first name, last name, and company domain.
Key Endpoints
43 endpoints — jentic publishes the only available openapi specification for apollo.
METHOD
PATH
DESCRIPTION
POST
/people/match
Enrich a single person record with email, phone, and firmographic data.
POST
/people/bulk_match
Bulk-enrich a list of person records in one call.
POST
/mixed_people/search
Search Apollo's people database with persona and account filters.
POST
/mixed_companies/search
Search Apollo's organisation database by firmographics.
GET
/organizations/enrich
Enrich a single organisation.
POST
/accounts
Create a CRM account.
POST
/contacts
Create a CRM contact.
POST
/opportunities
Create a deal in the pipeline.
POST
/people/match
Enrich a single person record with email, phone, and firmographic data.
POST
/people/bulk_match
Bulk-enrich a list of person records in one call.
POST
/mixed_people/search
Search Apollo's people database with persona and account filters.
POST
/mixed_companies/search
Search Apollo's organisation database by firmographics.
GET
/organizations/enrich
Enrich a single organisation.
POST
/accounts
Create a CRM account.
POST
/contacts
Create a CRM contact.
POST
/opportunities
Create a deal in the pipeline.
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Apollo x-api-key headers are stored in the encrypted Jentic vault (MAXsystem) and injected at call time. The raw key never enters the agent's context, which matters because the key inherits the workspace user's permissions across enrichment, search, and CRM writes.
Intent-based discovery
Agents search Jentic by intent (e.g., 'enrich a person' or 'search Apollo for marketing leaders') and receive the matching Apollo operation with its full input schema, so the agent does not have to map between Apollo's UI terminology and the underlying endpoint.
Time to first call
Direct Apollo integration: 2-4 days for auth, pagination, bulk endpoints, and 429 backoff. Through Jentic: under 2 hours once the API key is stored — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Apollo.Io API through Jentic.
Why is there no official OpenAPI spec for Apollo.Io API?
Apollo.io publishes its developer reference as HTML rather than an OpenAPI document. Jentic generates and maintains this spec so that AI agents and developers can call Apollo.Io 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 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. Sign up at https://app.jentic.com/sign-up.
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.
GET STARTED