Skip to content

Sales Intelligence

Apollo
API integration

Ship Sales Intelligence features without building the integration. Full Apollo API access via Proxy, normalized data through Unified APIs, and 4 MCP-ready tools for AI agents — all extensible to your exact use case.

Talk to us
Apollo

Use Cases

Why integrate with Apollo

Common scenarios for SaaS companies building Apollo integrations for their customers.

01

Enrich prospect records with verified contact data

SaaS companies building CRMs, ABM platforms, or lead management tools can let users pull enriched contact and company data from Apollo — including direct dials, verified emails, and firmographics — directly into their product without users leaving the app.

02

Automate outbound sequence triggers from external events

Products that capture buying signals (website visits, webinar signups, form fills) can programmatically push contacts into Apollo sequences, enabling users to act on intent data in real time without manual list building.

03

Sync user and team data for seat management and permissions

SaaS platforms that need to map their customers' Apollo team structures — for provisioning, access control, or reporting — can use the Unified User Directory API to pull Apollo user records and keep internal directories in sync.

04

Bi-directional activity sync between Apollo and a system of record

Niche CRMs, ATS platforms, or ERP tools can sync contacts, tasks, and engagement activity with Apollo so sales reps avoid double data entry and always have up-to-date prospect context in both systems.

05

Power candidate sourcing with Apollo enrichment in recruiting tools

ATS and recruiting SaaS products can let recruiters paste a LinkedIn URL or email and instantly hydrate the candidate profile with Apollo's people data — personal email, phone number, work history — all within their existing workflow.

What You Can Build

Ship these features with Truto + Apollo

Concrete product features your team can ship faster by leveraging Truto’s Apollo integration instead of building from scratch.

01

One-click contact enrichment from partial data

Let users input an email address or company domain and automatically return verified phone numbers, job titles, LinkedIn URLs, and company firmographics from Apollo.

02

Event-driven sequence injection

Automatically add or remove contacts from Apollo outbound sequences when your product detects a trigger event like a pricing page visit, demo request, or form submission.

03

Apollo user directory sync via Unified API

Use Truto's Unified User Directory API to pull Apollo user records into your app for team mapping, seat-based provisioning, or internal permission management.

04

Bulk enrichment pipeline with rate-limit handling

Ship a CSV upload or list-based enrichment feature that processes records through Apollo's bulk endpoints while Truto manages pagination, throttling, and retry logic behind the scenes.

05

Automated follow-up task creation in Apollo

Push 'Call Prospect' or 'Send Follow-Up' tasks directly into an SDR's Apollo dashboard based on engagement signals captured in your product.

06

Bi-directional contact and activity sync

Keep contacts, company records, and engagement logs (email opens, calls made) synchronized between your product and Apollo so reps always work from a single source of truth.

SuperAI

Apollo AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

apollo_people_enrichment_match

Find one person by email, LinkedIn URL, or a name (name, or first_name and last_name) together with the company they work at (organization_name or domain), and return their enriched profile. Costs 1-9 credits when a person is matched (more if a mobile phone is revealed), 0 credits on no match. Every parameter is sent as a query-string parameter, even though the HTTP method is POST -- Apollo's own OpenAPI spec marks every one of them `in: query`, and no JSON body is sent. Phone numbers cannot be revealed through this integration: reveal_phone_number triggers an asynchronous webhook/poll flow that is not offered here.

apollo_organizations_enrich

Find one company by domain, LinkedIn URL, or website (name alone is not accepted -- Apollo returns 422 -- but it narrows the match when sent alongside another identifier), and return its enriched profile. 1 credit per organization matched. Every parameter is sent as a query-string parameter; no JSON body is sent. This is a separate method from the pre-existing organization-enrichment.list (added before unified enrichment existed): that method's `list` resource-method type makes the engine apply the integration's inherited page-format pagination unconditionally, adding `page`/`per_page` query parameters this endpoint does not document; this `enrich` method is a custom-named method, so no pagination logic runs and no undocumented parameters are added.

list_all_apollo_mixed_people

Search for people. 0 credits. Requires a master API key, or a key with the mixed_people_api_search OAuth scope -- a normal API key gets a 403 "endpoint access denied". Results are partial: there is no email or phone field at all in this search response (only boolean has_email/has_direct_phone flags), and the last name is masked (last_name_obfuscated, e.g. "Hu***n") rather than withheld outright, so every record from this method is partial. Every filter and the page/per_page pagination parameters are sent as query-string parameters, even though the HTTP method is POST.

list_all_apollo_mixed_companies

Search for companies. 1 credit per page (unlike the people-search sibling, this is not free). Records here are full, not masked. Every filter and the page/per_page pagination parameters are sent as query-string parameters, even though the HTTP method is POST.

Why Truto

Why use Truto’s MCP server for Apollo

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 850+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

Unified APIs

Unified APIs for Apollo

Skip writing code for every integration. Use Truto’s category-specific Unified APIs out of the box or customize the mappings with AI.

Unified Enrichment API

Company

Represents a company as known to a sales intelligence or data enrichment provider: who it is, what it does, how big it is and where it is. A provider fills only the fields it has data for and omits the rest.

View Docs

Person

Represents a person as known to a sales intelligence or data enrichment provider: who they are, their current job and how to contact them. A provider fills only the fields it has data for and omits the rest.

View Docs

Unified User Directory API

Users

The User object represents a User.

View Docs

How It Works

From zero to integrated

Go live with Apollo in under an hour. No boilerplate, no maintenance burden.

01

Link your customer’s Apollo account

Use Truto’s frontend SDK to connect your customer’s Apollo account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call Apollo

Truto’s Proxy API is a 1-to-1 mapping of the Apollo API. You call us, we call Apollo, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate Apollo’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Apollo on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

What authentication method does Apollo use for API access?

Apollo uses API key-based authentication. End users generate an API key from their Apollo account settings, and Truto securely manages the credential storage and injection for each connected account.

What are Apollo's API rate limits, and how does Truto help?

Apollo enforces strict rate limits, typically capped at around 200 requests per minute on paid tiers. Truto's abstraction layer handles automatic rate-limit throttling, retry logic, and request queuing so your integration degrades gracefully under load.

Which Truto Unified APIs are available for Apollo today?

Apollo is currently supported through Truto's Unified User Directory API for syncing user records. Additional tools and unified API categories (enrichment, sequences, contacts) can be built on request to match your specific use case.

How does Truto handle Apollo's paginated search results?

Apollo's search endpoints return paginated responses that can be complex to manage. Truto abstracts pagination automatically, presenting results as a simple iterable list so your developers don't need to implement cursor or offset logic.

Can I use Apollo's bulk enrichment endpoints through Truto?

Apollo supports bulk enrichment processing up to 10 records per API call. Truto can be configured to batch and manage these requests, handling polling and rate limits so your product can offer bulk enrichment without hitting API ceilings.

What happens if a specific Apollo endpoint I need isn't available as a Truto tool yet?

Truto builds integration tools on request. If you need access to a specific Apollo endpoint — such as sequence management, task creation, or organization enrichment — the Truto team can scope and ship it based on your requirements.

Apollo

Get Apollo integrated into your app

Our team understands what it takes to make a Apollo integration successful. A short, crisp 30 minute call with folks who understand the problem.