Source connector

Lever connector

Lever integration for databases, warehouses and BI tools

Applicant tracking and candidate relationship management. Datrise captures Lever entities such as candidates, opportunities, postings, interviews, offers and feedback forms, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Lever (Data) API v1 authenticates with API key, OAuth 2.0, incremental runs key on updatedAt (milliseconds since epoch), and Lever caps calls at 10 requests/second per API key steady-state, with bursts tolerated up to 20 requests/second (token bucket).

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `lever_candidates`) with a schema derived from the Lever API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Lever pipeline page, and join the waitlist to get the Lever connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Lever data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
candidates	lever_candidates	Upsert by primary key, incremental on updated-at
opportunities	lever_opportunities	Upsert by primary key, incremental on updated-at
postings	lever_postings	Upsert by primary key, incremental on updated-at
interviews	lever_interviews	Upsert by primary key, incremental on updated-at
offers	lever_offers	Upsert by primary key, incremental on updated-at
feedback forms	lever_feedback_forms	Upsert by primary key, incremental on updated-at

Lever API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Lever (Data) API v1
Authentication	API key, OAuth 2.0 — Customer integrations authenticate with Basic Auth using an API key as the username and a blank password; partner integrations use an OAuth 2.0 authorization-code flow.
Pagination	cursor — List endpoints take limit (1-100, default 100) plus an opaque offset value copied from the previous response's next token, returned alongside a hasNext boolean.
Rate limit	10 requests/second per API key steady-state, with bursts tolerated up to 20 requests/second (token bucket)
Incremental cursor	updatedAt (milliseconds since epoch) — createdAt/updatedAt are available per resource, but deleted applications are not reflected as a delta on updatedAt and require the dedicated deleted-records endpoint.
Webhooks	Yes — Lever webhooks (HMAC-SHA256 signed; e.g. candidateHired, candidateStageChange, applicationCreated)
Bulk export	No
Deletes detectable	Yes — The applications/deleted endpoint filters by deleted_at_start/deleted_at_end; archived opportunities separately carry archivedAt and archiveReason fields rather than being removed

Official API reference

What bites when replicating Lever

Steady-state throttle is 10 requests/second per API key with bursts only tolerated to 20 requests/second, so large historical backfills need client-side throttling, not just retry-on-429.
Deleted records are not visible via a delta on updatedAt; use the dedicated applications/deleted endpoint filtered by deleted_at_start/deleted_at_end to detect them.
Archived opportunities remain retrievable and carry `archivedAt` plus an `archiveReasonId` rather than being removed, so archived status must be read as a field, not treated as a delete signal.
List pagination caps limit at 100 per page, so large candidate/opportunity backfills require many round trips using the offset/next token pair.

Compare this against every other documented API

Popular destinations for Lever

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Lever connector FAQ

What Lever data does the connector extract?: 6 objects: candidates, opportunities, postings, interviews, offers and feedback forms. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Lever integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Lever data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Lever → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Lever pipeline with guided onboarding

Join the waitlist to get priority access for Lever integrations with guided setup, schema-aware mapping, and production-grade incremental sync.