Connectors › Apollo

Apollo enrich

Reveal one searched Apollo person by id: email, full name, LinkedIn, location and company details, one credit per match.

Connectorapollo/enrich
Roleenrich
Recordsperson
Tierverified since 2026-09-27
CredentialAPOLLO_API_KEY stored once with gtme secret set APOLLO_API_KEY
Cost$0.01 per record estimated; the receipt shows what was spent
Cache30 days: a re-run inside the window reads the ledger instead of paying again
CallsPOST https://api.apollo.io/api/v1/people/match
Sourcegithub.com/gtme-run/gtme-bindings/apollo-enrich

Use it

Install it from the registry. Nothing installs unverified: the fixtures run offline first.

gtme adapters add github.com/gtme-run/gtme-bindings/apollo-enrich@main

The command prints the hosts the binding will call and the credentials it will ask for, then pins the commit it fetched. Then, in a pipeline file:

steps:
  - id: enrich
    use: apollo/enrich

gtme plan pipeline.yaml checks the credential is set and that every field this step needs is provided by a step before it, without calling anyone.

Needs

apollo.id

Provides

email, email_status, first_name, last_name, full_name, title, seniority, linkedin_url, city, state, country, company_name, company_domain, company_website, company_linkedin_url, company_industry, company_employees

Config

KeyTypeWhat it does
reveal_personal_emailsbooleanAsk Apollo to include personal emails (their flag; off by default)
base_urlstringOverride the API host (testing) Default https://api.apollo.io.

What a response looks like

Recorded from a real response to POST /api/v1/people/match, status 200. The conformance kit proves this payload in produces canonical records out, and gtme run --simulate serves it in place of the network.

{
  "person": {
    "id": "5f3b0c1a2d",
    "first_name": "Jane",
    "last_name": "Doe",
    "name": "Jane Doe",
    "title": "VP Marketing",
    "seniority": "vp",
    "email": "jane.doe@acme.com",
    "email_status": "verified",
    "linkedin_url": "http://www.linkedin.com/in/jane-doe",
    "city": "Austin",
    "state": "Texas",
    "country": "United States",
    "organization": {
      "id": "org_1",
      "name": "Acme Inc",
      "website_url": "http://www.acme.com",
      "primary_domain": "acme.com",
      "linkedin_url": "http://www.linkedin.com/company/acme",
      "industry": "software",
      "estimated_num_employees": 120
    }
  },
  "request_id": "req_fixture_1"
}

On this page, connector means what gtme calls an adapter. This one is a binding from the registry. Two adapter tiers explains the difference.