- Two routes catalogued: people match (POST /people/match) and organization enrich (GET /organizations/enrich)
- People match by name, e-mail, company name, domain or LinkedIn URL; organization enrich by domain, LinkedIn URL, name or website
- Contact Enrich in Iris fills job title, location, LinkedIn URL, e-mail and phone when they are empty
- Keeps headline, seniority, departments and company on the contact as a source record
- Runs on your own Apollo API key; Apivom Atlas stores nothing
Apollo.io People and Organization Enrich
Apollo's people-match and organization-enrich endpoints in Apivom Atlas, connected to Apivom Iris with your own Apollo API key: match a contact by name, e-mail, company, domain or LinkedIn URL and fill the empty fields on the record, without Apivom ever holding your credential.
What you can do
Use cases
- Complete a lead from an event list — Add the name and company from a badge scan, run Enrich via Apollo, and get the work e-mail, job title and LinkedIn URL on the contact.
- Fill in a contact that only has a LinkedIn URL — A contact with nothing but a profile address gets its job title, location, e-mail and phone filled in one step, when Apollo returns them.
- Look a company up by domain — The organization enrich route resolves a company from its domain, LinkedIn URL, name or website, for integrations we scope with you.
Apollo.io is a B2B sales intelligence platform with a REST API. Apivom Atlas catalogues two routes: people match, where you send what you know about a person, such as name, e-mail, company name, domain or LinkedIn URL, and Apollo returns the matching profile; and organization enrich, which looks a company up by domain, LinkedIn URL, name or website. Apivom Iris uses people match as one of the providers in the Enrich menu on a contact: it fills job title, location, LinkedIn URL, e-mail and phone when they are empty and keeps Apollo's headline, seniority, departments and company as a source record. Calls run with your own Apollo API key, sent as the x-api-key header; Iris keeps the key encrypted in your tenant and Apivom Atlas stores nothing.
Authentication
Your own Apollo API key (Apollo Settings → Integrations → API), sent as the x-api-key header. Stored encrypted in your Apivom Iris tenant; Apivom Atlas forwards the call and stores no credentials.
Frequently asked questions
Which Apollo endpoints does the connector cover?
Two: people match (POST /people/match) and organization enrich (GET /organizations/enrich). Other Apollo endpoints are not catalogued.
What do I need to run a people match?
At least a name, an e-mail or a LinkedIn URL. A company name and domain sharpen the match. A lookup without a match is reported and nothing is saved.
Does Apivom sell Apollo data or charge per lookup?
No. Apivom does not sell or resell Apollo data. You connect your own Apollo account, and Apollo's terms, quotas and pricing apply to every lookup. Apivom adds no per-lookup fee for this connector.
Where are my Apollo credentials stored?
In your Apivom Iris tenant, encrypted. Apivom Atlas is a stateless gateway: it forwards each call to the provider and stores no credentials.
Can I use this connector from my own application?
Apivom Iris connects it today, and every route is catalogued in Apivom Atlas. Connecting it to your own applications is scoped per customer: tell us the use case and we plan it with you.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.