Skip to main content Skip to complementary content
Already have an account? Sign in

Lever (v1)

Last updated: 9/15/2026

Lever integration summary

Stitch’s Lever integration replicates data using the Lever API (v1). Refer to the Schema section for a list of objects available for replication.

Lever feature snapshot

A high-level look at Stitch's Lever (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Released on June 1, 2020

Supported by

Singer Community

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-lever

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Lever

Lever setup requirements

To set up Lever in Stitch, you need:

  • Super Admin privileges. Your role in Lever must be Super Admin in order to obtain an API Key.

Step 1: Obtain your API token

  1. Login to your Lever account.
  2. Hover over your account icon in the upper right corner of the page and click Settings.
  3. On the settings page, click API Credentials.
  4. On the API Credentials page, locate the Generate New Key link in the Lever API credentials section.
  5. If you would like your key to access confidential information, click on the Allow access to confidential data toggle. If not, skip to the next step.
  6. Click Done.

Keep your API key readily available for the next step.

Step 2: Add Lever as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Lever icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Lever” would create a schema called stitch_lever in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the Token field, paste the API Key you obtained in Step 1.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Lever integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Lever’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Lever integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For Lever integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab
    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

After you finish setting up Lever, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Lever table reference

archive_reasons

The archive_reasons table contains info about the reasons candidates have exited your active hiring pipeline. Refer to Lever’s documentation for more info.

Replication Method

Full Table

Primary Key

id

Useful links

Lever documentation

archive_reasons schema on GitHub

Lever API method

candidate_applications

The candidate_applications table contains info about candidate applications in your Lever account.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Lever documentation

candidate_applications schema on GitHub

Lever API method

candidate_offers

The candidate_offers table contains data sent to candidates about opportunities via Lever’s Offers feature.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Lever documentation

candidate_offers schema on GitHub

Lever API method

candidate_referrals

The candidate_referrals table contains info about the referrals in your Lever account.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Lever documentation

candidate_referrals schema on GitHub

Lever API method

candidate_resumes

The candidate_resumes table contains info about candidate resumes.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Lever documentation

candidate_resumes schema on GitHub

Lever API method

candidates

The candidates table contains info about candidates, or individuals who’ve been added to your Lever account as potential fits for job opportunities.

Note: This table must be set to replicate in order to replicate the candidate_applications, candidate_offers, candidate_referrals, and candidate_resumes tables.

During Extraction, this table will be replicated before any other selected candidate_* tables. Then, for every candidate, Stitch will query for every candidate’s applications, offers, referrals, and resumes.

For example: During Extraction, Stitch replicates a candidate with id: 12345 from Lever’s /candidates endpoint.

Using id: 12345, Stitch will then query for the rest of the candidate’s data:

  • /candidates/12345/applications
  • /candidates/12345/offers
  • /candidates/12345/referrals
  • /candidates/12345/resumes

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Lever documentation

candidates schema on GitHub

Lever API method

opportunities

The opportunities table contains info about opportunities. In Lever, an opportunity represents each of an individual candidate’s unique candidacies or journeys through your hiring pipeline for a position. A candidate can be associated with multiple opportunities.

Note: This table must be set to replicate in order to replicate the opportunity_applications, opportunity_offers, opportunity_referrals, and opportunity_resumes tables.

During Extraction, this table will be replicated before any other selected opportunity_* tables. Then, for every opportunity, Stitch will query for every opportunity’s applications, offers, referrals, and resumes.

For example: During Extraction, Stitch replicates an opportunity with id: 12345 from Lever’s /opportunities endpoint.

Using id: 12345, Stitch will then query for the rest of the opportunity’s data:

  • /opportunities/12345/applications
  • /opportunities/12345/offers
  • /opportunities/12345/referrals
  • /opportunities/12345/resumes

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Lever documentation

opportunities schema on GitHub

Lever API method

opportunity_applications

The opportunity_applications table contains info about candidate applications in your Lever account.

Note: To replicate this table, the opportunities table must be set to replicate.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

opportunity_applications schema on GitHub

Lever API method

opportunity_offers

The opportunity_offers table contains info about

Note: To replicate this table, the opportunities table must be set to replicate.

opportunity_referrals

The opportunity_referrals table contains info about the referrals in your Lever account.

Note: To replicate this table, the opportunities table must be set to replicate.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Lever documentation

opportunity_referrals schema on GitHub

Lever API method

opportunity_resumes

The opportunity_resumes table contains info about candidate resumes.

Note: To replicate this table, the opportunities table must be set to replicate.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Lever documentation

opportunity_resumes schema on GitHub

Lever API method

postings

The postings table contains info about job postings in your Lever account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updatedAt

Useful links

Lever documentation

postings schema on GitHub

Lever API method

requisitions

The requisitions table contains info about requisitions in your Lever account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

createdAt

Useful links

Lever documentation

requisitions schema on GitHub

Lever API method

sources

The sources table contains info about sources, or the ways that candidates enter into your Lever account.

Replication Method

Full Table

Primary Key

text

Useful links

Lever documentation

sources schema on GitHub

Lever API method

stages

The stages table contains info about stages, or the steps in the recruiting workflow in your hiring pipeline.

Replication Method

Full Table

Primary Key

id

Useful links

Lever documentation

stages schema on GitHub

Lever API method

users

The users table contains info about the users in your Lever account. A user includes anyone who has been invited to Lever to collaborate on recruiting efforts.

Replication Method

Full Table

Primary Key

id

Useful links

Lever documentation

users schema on GitHub

Lever API method

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!