This integration is powered by Singer's Lever tap. For support, visit the GitHub repo or join the Singer Slack.
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 | |
Stitch plan |
Standard |
API availability |
Available |
Singer GitHub repository | |||
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
- Login to your Lever account.
- Hover over your account icon in the upper right corner of the page and click Settings.
- On the settings page, click API Credentials.
- On the API Credentials page, locate the Generate New Key link in the Lever API credentials section.
- 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.
- Click Done.
Keep your API key readily available for the next step.
Step 2: Add Lever as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Lever icon.
-
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. - 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:
- For tables using Key-based Incremental Replication, data equal to or newer than this date will be replicated to your destination.
- For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your destination.
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:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
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:
-
Individual tables and columns
-
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’s Tables to Replicate tab, locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
-
Click the Tables to Replicate tab.
- In the list of tables, click the box next to the Table Names column.
-
In the menu that displays, click Track all Tables and Fields:
- 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.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
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
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 1 of this integration.
This is the latest version of the Lever integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs
> customers
), while case is maintained in PostgreSQL destinations (CusTomERs
> CusTomERs
). Refer to the Loading Guide for your destination for more info.
archive_reasons
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The archive_reasons
table contains info about the reasons candidates have exited your active hiring pipeline. Refer to Lever’s documentation for more info.
id
The archive reason ID. Reference: |
text
A description for the archive reason. For example: |
candidates
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
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
id
The candidate ID. |
||||||
applications
The ID of the candidate’s application.
|
||||||
archived
Details about the candidate’s archived status.
|
||||||
contact
The candidate’s contact ID. Reference: |
||||||
createdAt
The datetime when the candidate was created in Lever. |
||||||
dataProtection
Details about the candidate’s data protection status, based on candidate-provided consent and applicable data policy regulations. If there isn’t a policy in place or if no policies are applicable to the candidate, the values of these fields may be
|
||||||
emails
A list of emails for the candidate. |
||||||
followers
A list of IDs of the users following the candidate. |
||||||
headline
The candidate’s headline. This is typically a list of previous companies where the candidate has worked or schools the candidate has attended. |
||||||
isAnonymized
If |
||||||
lastAdvancedAt
The datetime when the candidate advanced to the current |
||||||
lastInteractionAt
The datetime when the last interaction with candidate occurred. |
||||||
links
A list of links for the candidate. |
||||||
location
The candidate’s current location. |
||||||
name
The candidate’s full name. |
||||||
origin
The way the candidate was added to Lever. Possible values are:
|
||||||
owner
The ID of the owner of the candidate. Reference:
|
||||||
phones
A list of phone numbers for the candidate.
|
||||||
resume
Details about the candidate’s resume. |
||||||
snoozedUntil
If the candidate is snoozed, this field will reflect the datetime when the snooze period ends. |
||||||
sources
A list of sources associated with the candidate. |
||||||
stage
The ID of the candidate’s current stage. Reference: |
||||||
stageChanges
Historical details of the candidate’s stage changes. |
||||||
tags
A list of tags applied to the candidate.
candidates (table), tags (attribute)
|
||||||
urls
A list of list and show URLs for the candidate.
|
candidate_applications
Replication Method : |
Key-based Incremental |
Replication Key |
candidates.updated_at |
Primary Key |
id |
API endpoint : |
The candidate_applications
table contains info about candidate applications in your Lever account.
candidate_offers
Replication Method : |
Key-based Incremental |
Replication Key |
candidates.updated_at |
Primary Key |
id |
API endpoint : |
The candidate_offers
table contains data sent to candidates about opportunities
via Lever’s Offers feature.
id
The offer ID. Reference: |
|||||||
approvedAt
The datetime when the offer was approved. |
|||||||
createdAt
The datetime when the offer was created. |
|||||||
creator
The ID of the offer creator. Reference:
|
|||||||
fields
Details about the fields on the offer. This includes standard fields and all custom fields.
|
|||||||
sentAt
The datetime when the offer was sent. |
|||||||
signatures
Details about the signature(s) associated with the offer.
|
|||||||
status
The status of the offer. Possible values are:
|
candidate_referrals
Replication Method : |
Key-based Incremental |
Replication Key |
candidates.updated_at |
Primary Key |
id |
API endpoint : |
The candidate_referrals
table contains info about the referrals in your Lever account.
id
The referral ID. Reference: |
||||||||
baseTemplateId
The form template ID associated with the referral. |
||||||||
completedAt
The datetime the referral was completed. |
||||||||
createdAt
The datetime the referral was created. |
||||||||
fields
Details about the fields on the referral form.
|
||||||||
instructions
The instructions on the referral form. |
||||||||
referrer
The ID of the referrer. Reference:
|
||||||||
stage
The stage of the candidate at the time the form was completed. |
||||||||
text
The title of the referral form. |
||||||||
type
The form type. |
||||||||
user
The ID of the referral creator. Reference:
|
candidate_resumes
Replication Method : |
Key-based Incremental |
Replication Key |
candidates.updated_at |
Primary Key |
id |
API endpoint : |
The candidate_resumes
table contains info about candidate resumes.
id
The resume ID. Reference: |
||||||||||||||||||||||
createdAt
The datetime when the resume was created in Lever. |
||||||||||||||||||||||
file
Metadata about the resume file.
|
||||||||||||||||||||||
parsedData
The candidate’s parsed resume, usually extracted from an attached PDF/Word document or online profile.
|
opportunities
Replication Method : |
Key-based Incremental |
Replication Key |
updated_at |
Primary Key |
id |
API endpoint : |
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
id
The opportunity ID. Reference: |
||||||
applications
The ID of the candidate’s application.
|
||||||
archived
Details about the opportunity’s archived status.
|
||||||
contact
The opportunity’s contact ID. Reference: |
||||||
createdAt
The datetime when the opportunity was created in Lever. |
||||||
dataProtection
Details about the opportunity’s data protection status, based on opportunity-provided consent and applicable data policy regulations. If there isn’t a policy in place or if no policies are applicable to the opportunity, the values of these fields may be
|
||||||
emails
A list of emails for the opportunity. |
||||||
followers
A list of IDs of the users following the opportunity.
|
||||||
headline
The contact’s headline. This is typically a list of previous companies where the contact has worked or schools the contact has attended. |
||||||
isAnonymized
If |
||||||
lastAdvancedAt
The datetime when the candidate advanced to the current |
||||||
lastInteractionAt
The datetime when the last interaction with opportunity occurred. |
||||||
links
A list of links for the opportunity. |
||||||
location
The opportunity’s current location. |
||||||
name
The opportunity’s full name. |
||||||
origin
The way the opportunity was added to Lever. Possible values are:
|
||||||
owner
The ID of the owner of the opportunity. Reference:
|
||||||
phones
A list of phone numbers for the opportunity.
|
||||||
resume
Details about the opportunity’s resume. This field has been deprecated by Lever. |
||||||
snoozedUntil
If the opportunity is snoozed, this field will reflect the datetime when the snooze period ends. |
||||||
sources
A list of sources associated with the opportunity. |
||||||
stage
The ID of the opportunity’s current stage. Reference: |
||||||
stageChanges
Historical details of the opportunity’s stage changes.
|
||||||
tags
A list of tags applied to the opportunity.
opportunities (table), tags (attribute)
|
||||||
urls
A list of list and show URLs for the opportunity.
|
opportunity_applications
Replication Method : |
Key-based Incremental |
Replication Key |
opportunities.updated_at |
Primary Key |
id |
API endpoint : |
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.
id
The opportunity application ID. Reference: |
|||
archived
The application’s archived status.
|
|||
candidateId
The ID of the candidate associated with the application. Reference: |
|||
comments
Any additional comments from the candidate included in the application. |
|||
company
The candidate’s current company or organization. |
|||
createdAt
Datetime the application was created in Lever. |
|||
customQuestions
If application is |
|||
email
The email address of the candidate who applied. |
|||
links
A list of links associated with the candidate.
|
|||
name
The name of the candidate who applied. |
|||
phone
The phone numbers for the candidate.
|
|||
posting
The ID of the job posting associated with the application. Reference: |
|||
postingHiringManager
The hiring manager of the job posting at the time when the candidate applies to that job. Reference:
|
|||
postingOwner
The ID of the user who owned the job posting when the candidate applied to the job. Reference:
|
|||
requisitionForHire
If the application was archived as hired against a requisition, this is the data related to the requisition.
|
|||
resume
Details about the candidate’s resume. This field has been deprecated by Lever. |
|||
type
The type of application. Possible values are:
|
|||
user
If the application is a Reference:
|
opportunity_offers
Replication Method : |
Key-based Incremental |
Replication Key |
opportunities.updated_at |
Primary Key |
None |
API endpoint : |
The opportunity_offers
table contains info about
Note: To replicate this table, the opportunities
table must be set to replicate.
id
The offer ID. Reference: |
|||||||||||||||
approved
|
|||||||||||||||
approvedAt
The datetime when the offer was approved. |
|||||||||||||||
createdAt
The datetime when the offer was created. |
|||||||||||||||
creator
The ID of the offer creator. Reference:
|
|||||||||||||||
fields
Details about the fields on the offer. This includes standard fields and all custom fields.
|
|||||||||||||||
opportunityId
The ID of the opportunity associated with the offer. Reference: |
|||||||||||||||
posting
The ID of the posting associated with the offer. Reference: |
|||||||||||||||
sentAt
The datetime when the offer was sent. |
|||||||||||||||
sentDocument
Details about the document sent to the candidate.
|
|||||||||||||||
signatures
Details about the signature(s) associated with the offer.
|
|||||||||||||||
signedDocument
Details about the signed offer file.
|
|||||||||||||||
status
The status of the offer. Possible values are:
|
opportunity_referrals
Replication Method : |
Key-based Incremental |
Replication Key |
opportunities.updated_at |
Primary Key |
id |
API endpoint : |
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.
id
The referral ID. Reference: |
||||||||
baseTemplateId
The form template ID associated with the referral. |
||||||||
completedAt
The datetime the referral was completed. |
||||||||
createdAt
The datetime the referral was created. |
||||||||
fields
Details about the fields on the referral form.
|
||||||||
instructions
The instructions on the referral form. |
||||||||
referrer
The ID of the referrer. Reference:
|
||||||||
stage
The stage of the candidate at the time the form was completed. |
||||||||
text
The title of the referral form. |
||||||||
type
The form type. |
||||||||
user
The ID of the referral creator. Reference:
|
opportunity_resumes
Replication Method : |
Key-based Incremental |
Replication Key |
opportunities.updated_at |
Primary Key |
id |
API endpoint : |
The opportunity_resumes
table contains info about candidate resumes.
Note: To replicate this table, the opportunities
table must be set to replicate.
id
The resume ID. Reference: |
||||||||||||||||||||||
createdAt
The datetime when the resume was created in Lever. |
||||||||||||||||||||||
file
Metadata about the resume file.
|
||||||||||||||||||||||
parsedData
The candidate’s parsed resume, usually extracted from an attached PDF/Word document or online profile.
|
postings
Replication Method : |
Key-based Incremental |
Replication Key |
updatedAt |
Primary Key |
id |
API endpoint : |
The postings
table contains info about job postings in your Lever account.
id
The job posting ID. Reference: |
||||||
updatedAt
The datetime when the posting was last updated. |
||||||
categories
|
||||||
content
The content of the posting, including any custom questions.
|
||||||
createdAt
The datetime when the posting was created. |
||||||
distributionChannels
A list of job sites that a
|
||||||
followers
A list of IDs of users following the posting.
|
||||||
hiringManager
The user ID of the hiring manager for the job posting. Reference:
|
||||||
owner
The ID of the posting owner. The posting owner is the user who is responsible for managing all candidates who applied to the position. Reference:
|
||||||
reqCode
The requisition code associated with the posting. This field has been deprecated by Lever. |
||||||
state
The posting’s current status. Refer to Lever’s documentation for a list of possible values. |
||||||
tags
A list of additional posting tags.
postings (table), tags (attribute)
|
||||||
text
The title of the job posting. |
||||||
urls
A list of the list, show, and apply URLs for the posting.
|
||||||
user
The ID of the user who created the posting. Reference:
|
requisitions
Replication Method : |
Key-based Incremental |
Replication Key |
createdAt |
Primary Key |
id |
API endpoint : |
The requisitions
table contains info about requisitions in your Lever account.
id
The requisition ID. Reference: |
||||
createdAt
The datetime when the requisition was created. |
||||
backfill
If |
||||
compensationBand
Details about the compensation band associated with the requisition band.
|
||||
creator
The user ID of the requisition’s creator. Reference:
|
||||
customFields
The custom fields associated with the requisition. |
||||
department
|
||||
employmentStatus
The work type of the requisition. Possible values are:
|
||||
headcountHired
The number of filled seats or openings on the requisition. |
||||
headcountTotal
The total headcount alloted for this requisition. |
||||
hiringManager
The user ID of the hiring manager for this requisition. Reference:
|
||||
internalNotes
Details about the requisition. |
||||
location
The location associated with the requisition. |
||||
name
The name of the requisition. |
||||
offerIds |