Skip to content
CRM ⇄ Human resources

Apollo.io to Lever integration — real-time, two-way sync

Keep Apollo.io and Lever in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Apollo.io and Lever

Keep the people who own accounts in Apollo.io in step with the workforce records in Lever, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Apollo.io runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Lever. Lever is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Stacksync syncs Custom fields, Contacts, Accounts, People (database records) in Apollo.io with Postings, Requisitions, Offers, Users in Lever field by field, in real time, and in both directions. You decide which system owns which fields, so Lever stays authoritative on roles and org structure while Apollo.io keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Push CRM opportunity stages back into Apollo so reps see pipeline context while sequencing.
  • 02 Land sequence enrollment status and outcomes in a warehouse for outbound performance reporting.
  • 03 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.
  • 04 Two-way sync Opportunities and their Stages between Lever and a Postgres database so recruiting ops and analysts query the pipeline in SQL while recruiters keep working in Lever.

Common sync patterns

Deactivate access when someone leaves

When Lever marks a worker as departed, the matching user in Apollo.io is flagged or deactivated, so former employees do not keep CRM access after their last day.

One directory of people

A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.

Where Lever tracks people the business also engages: contacts stay in sync

A person recorded in Lever, such as a candidate or applicant, can create or update the matching contact in Apollo.io, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

What you can sync between Apollo.io and Lever

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Apollo.io objects Lever objects How this pairing syncs
Tasks and calls Rep activity records synced for activity reporting and coaching workflows. Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. Tasks and calls is specific to Apollo.io and Requisitions to Lever — each maps to any object or custom field on the other side.
Custom fields Account- and contact-level custom attributes mapped field-by-field in a sync. Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. Custom fields is specific to Apollo.io and Offers to Lever — each maps to any object or custom field on the other side.
Contacts People saved to your Apollo account, synced with emails, phone numbers, and enrichment fields. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Contacts is specific to Apollo.io and Users to Lever — each maps to any object or custom field on the other side.
Accounts Company records with firmographic attributes, matched to CRM accounts during sync. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Accounts is specific to Apollo.io and Stages to Lever — each maps to any object or custom field on the other side.
People (database records) Prospects from Apollo's global database, pulled into downstream systems once enriched or saved. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. People (database records) is specific to Apollo.io and Feedback to Lever — each maps to any object or custom field on the other side.
Sequences Outreach cadences (emailer campaigns in the API); enrollment status is read to track which contacts are being worked. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Sequences is specific to Apollo.io and Interviews to Lever — each maps to any object or custom field on the other side.

How changes propagate between Apollo.io and Lever

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Apollo.io Lever Interval-based propagation

DetectionStacksync polls Apollo.io for changes on an incremental schedule, reading only records changed since the previous pass. Polling on updated-at timestamps.

DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.

Lever Apollo.io Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryEach detected change is written to Apollo.io through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Apollo.io: Rate limits and enrichment credits vary by plan; bulk endpoints are throttled separately from single-record calls.
  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
What ships with Apollo.io ⇄ Lever

Connect Apollo.io and Lever for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apollo.io–Lever connection.

Real-time

Two-way sync

Changes in Apollo.io or Lever instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apollo.io or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Apollo.io or Lever record.

Observability

Monitoring

Track your Apollo.io ⇄ Lever sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apollo.io and Lever.

How the Apollo.io and Lever connectors work

Apollo.io

Integration surface
REST API
Authentication
API key (passed in request headers); master keys unlock account-wide endpoints
Change detection
Polling on updated-at timestamps; webhook callbacks exist only for delivering asynchronous enrichment results, not as a general change-event stream
Capabilities
read · write
Rate limits
Rate limits and enrichment credits vary by plan; bulk endpoints are throttled separately from single-record calls

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide
How it works

How to connect Apollo.io to Lever — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Apollo.io and Lever with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Apollo.io connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apollo.io and Lever objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Apollo.io ⇄ Lever
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Apollo.io Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apollo.io and Lever integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 408 integrations available for Apollo.io and Lever.

Popular · 7 of 408
All Apollo.io integrations All Lever integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own