Skip to content
Human resources

Connect Lever to any app with two-way sync.

Two-way sync Lever across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Lever.

These objects sync between Lever and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Lever exposes them.

Opportunities
The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS.
Postings
Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting.
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.
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.
Users
Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API.
Stages
Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database.
Feedback
Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics.
Interviews
Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint.
Notes and Contacts
Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution.
API surface

How Stacksync connects to Lever.

The connector runs on Lever's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
Lever connector documentation
What ships with Lever

Connect Lever for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Lever instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever 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 Lever record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Lever connector.

Lever is an applicant tracking system and recruiting CRM owned by Talent Acquisition and Recruiting Operations, with HR and People Ops as stakeholders. It is the system of engagement for hiring: Opportunities (candidates), Postings, Requisitions, Offers, interview Feedback, and pipeline Stages all live there, alongside sourcing attribution. Because every open role, candidate interaction, and hiring decision is recorded in Lever, downstream HRIS, analytics, and onboarding tools need to read from and write back to it.

  • Talent Acquisition / Recruiting Operations
  • HR / People Ops
  • Data engineering
  • Lever administrators
  • Hiring managers
  1. 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.

  2. Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.

  3. When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.

  4. Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.

  5. Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.

  6. 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's UI.

All Lever integrations

Pick the system you need to keep in sync with Lever. Each page covers the sync setup, field mapping, and common workflows for that pair.

How it works

Set up Lever in minutes, without APIs.

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 Lever with its 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
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Lever objects to sync — Stacksync auto-detects the schema, 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 · 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
    Lever database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp

FAQ

Lever connector FAQ

What can I sync with the Lever connector?

Lever's core objects — Opportunities, Postings, Requisitions, Offers and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Lever?

Via REST Data API (api.lever.co/v1), authenticated with 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). Changes are detected as follows — 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. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Lever connector two-way?

Yes. Changes made in Lever propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Lever integration take to set up?

Most Lever integrations go live in minutes: authenticate Lever and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Lever data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Lever data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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.

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:

Coworkers laughing in front of a laptop in a casual office setting

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