Reference · built on requestConnectorCRM & sales

Apollo

Contacts, accounts, sequences, and people and organization enrichment from Apollo through its REST API.

Request accessPricing ↗

About

Apollo is a sales intelligence and engagement platform with its own contact database. Its REST API groups endpoints into search and enrich, manage records, engage, workspace management, and analytics. Enrichment is metered in credits: a people match charges 1 credit for demographics or an email and 8 more if a mobile phone is returned, and nothing when no data is found. Rate limits are set per team and per plan across minute, hour, and day windows.

An operator on Fibric enriches a new lead, checks for an existing contact, and proposes a contact record or a sequence add. You approve each one, the write runs once, and a receipt records what changed, why, how to undo it, and the credits spent.

This is a reference listing. It documents what Fibric would read from Apollo and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • People enrichment through POST /api/v1/people/match by name, email, domain, or linkedin_url, with match_confidence high, medium, low, or none
  • Organization search through POST /api/v1/mixed_companies/search by headcount range, location, keyword tags, and name
  • Contacts and accounts in your workspace, with run_dedupe matching at creation
  • Sequences, emails, calls, tasks, and conversations under the engage endpoints
  • Users and workspace metadata, some of which need a master API key
  • API usage stats, including the rate limits assigned to your team

Proposed actions

  • Target capability: propose a contact through POST /api/v1/contacts, with run_dedupe set so an existing match is updated in place
  • Target capability: propose adding contacts to a sequence through POST /api/v1/emailer_campaigns/{sequence_id}/add_contact_ids
  • Target capability: propose an enrichment request that spends credits, with the credit estimate shown first

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Fill in a lead before you route it

    Run people match on the lead's email and domain, read the returned organization and title, and propose the enriched contact with an owner for approval.

    With Lead Response

  • Stop the same person entering twice

    Create contacts with run_dedupe true so a matching record is updated in place, and show the owner the existing id instead of a second record.

    With Duplicate Lead

  • Balance territories on real headcount

    Search organizations by employee range and location, and propose account reassignments with the counts behind each move.

    With Territory Balance

  • Check a new trade account's company

    Match the applicant's domain to an organization record and propose approve, hold, or ask for more, with the enrichment attached.

    With Account Application

Requirements

  • An Apollo workspace and an admin who can create an API key; requests are attributed to the workspace's longest-standing active admin
  • A master API key for endpoints such as listing users or adding contacts to a sequence
  • A paid plan and a work-email registration for organization search and some search, enrichment, and record-retrieval endpoints
  • Enough credits for enrichment, since demographics, email, and mobile phone results are charged per match
Authentication
An API key sent in the x-api-key header; a master key reaches every endpoint, a standard key only the endpoints it was granted, and apps built for other teams use OAuth 2.0.

Limits

  • Rate limits are per team and per plan on minute, hour, and day windows; a 429 carries a retry-after header
  • Organization search shows at most 50,000 records per query, 100 per page across 500 pages, and costs 1 credit per page
  • Phone and waterfall enrichment need a webhook_url or poll_only, because results arrive after the first response
  • Requests made with an API key act as the workspace's earliest-created active admin, not as the key's creator

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Apollo ↗

Questions and answers

When does Apollo charge credits?
Only when credit-consuming data is found. A people match charges 1 credit for demographics or an email, plus 8 credits if a mobile phone is returned, and 0 credits when nothing surfaces or match_confidence is none. Creating a contact and adding contacts to a sequence cost 0 credits.
What is the difference between a master and a standard API key?
A master key grants access to all endpoints. A standard key has limited access, and endpoints such as listing users or adding contacts to a sequence require the master key. Both go in the x-api-key header.
How do I find my team's rate limits?
Call the view API usage stats endpoint, which returns the rate limits currently assigned to your team. Limits differ by plan and by endpoint group, responses carry rate-limit, usage, and requests-left headers, and a 429 includes retry-after with the wait time.
Ask about Apollo

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Apollo through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy