Lever is a modern applicant tracking system (ATS) for recruiting and hiring. This connector uses the Lever Data API to read and write opportunities (candidates), postings, applications, interviews, feedback, notes, offers, referrals, requisitions, stages, and tags, so you can sync your hiring pipeline with the rest of your data stack.
Power end-to-end data operations for your Lever Hiring API with Nexla. Our bi-directional Lever Hiring connector is purpose-built for Lever Hiring, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Lever Hiring or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Lever Hiring workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Lever Hiring credential, you need a Lever API key. The Lever Data API authenticates with HTTP Basic Auth, where your API key is used as the username and the password is left blank.
To obtain your Lever API key, follow these steps:
Sign in to your Lever account with an administrator that has permission to manage integrations.
Open Settings and navigate to the Integrations and API page.
Select the API Credentials tab.
Generate a new API key. During creation, you can choose whether the key is granted access to confidential data, and you can maintain multiple active keys at once.
Copy the API key and store it securely. Lever API keys carry broad privileges, so treat the key as a secret and revoke it if it is ever exposed.
The base URL for the Lever Data API is https://api.lever.co. For more details on authentication, available resources, and response formats, see the Lever Developer Documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Lever API key in the API Key field. This value is used as the username for HTTP Basic Auth.
Leave the Password field blank, as required by Lever's API key authentication.
Enter the base URL for the Lever Data API in the Base URL field. Unless you have been directed to use a different host, this is https://api.lever.co.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Lever API keys carry many privileges. Keep the key confidential, and if it is ever exposed, revoke it on the Integrations and API page in Lever Settings and generate a new one. For more information, see the Lever Developer Documentation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Lever Hiring connector tile, then select the credential that will be used to connect to Lever, and click Next; or, create a new Lever Hiring credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Lever endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List Opportunities
Returns a list of all opportunities (candidates) in the hiring pipeline.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever API Documentation.
[Rest API] List Users
Returns a list of all users (team members) in the organization.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever API Documentation.
[Rest API] List Applications
Returns a list of all applications submitted by candidates.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever API Documentation.
[Rest API] List Interviews
Returns a list of all scheduled interviews in the hiring process.
This endpoint requires an Opportunity ID identifying the Lever opportunity whose interviews to list.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever API Documentation.
[Rest API] List Notes
Returns a list of all notes associated with opportunities.
This endpoint requires an Opportunity ID identifying the opportunity to retrieve notes for.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever API Documentation.
[Rest API] List Offers
Returns a list of all offers extended to candidates.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever API Documentation.
[Rest API] List Referrals
Returns a list of all employee referrals submitted in the system.
This endpoint requires an Opportunity ID identifying the Lever opportunity whose referrals to list.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever API Documentation.
[Rest API] Get applicant
Retrieves details for a specific applicant by ID.
This endpoint accepts an Id path parameter identifying the opportunity to retrieve.
Returns a paginated list of job positions in the ATS system.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever Developer Documentation.
[Rest API] Get job
Retrieves details for a specific job position by ID.
This endpoint accepts an Id path parameter identifying the job posting to retrieve.
List all pipeline stages defined in the Lever account.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever Developer Documentation.
[Rest API] List interview feedback
List all interview feedback/scorecard forms for a candidate opportunity.
This endpoint requires an Opportunity ID identifying the candidate opportunity.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever Developer Documentation.
[Rest API] List requisitions
List all requisitions (headcount requests linked to job postings).
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever Developer Documentation.
[Rest API] List tags
List all candidate tags defined in the Lever account.
Results are paginated. Nexla automatically follows Lever's cursor-based pagination to fetch subsequent pages of data. For details on the response structure and available fields, see the Lever Developer Documentation.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Lever Hiring data sources can also be manually configured to ingest data from any valid Lever Data API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Lever Hiring data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Lever Hiring destination, and select the Send to Destination option from the menu. Select the Lever Hiring connector from the list of available destination connectors, then select the credential that will be used to connect to Lever, and click Next; or, create a new Lever Hiring credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Lever endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Create applicant
Creates a new applicant in the ATS system.
Each record from your Nexset is sent as a JSON request body to create a new opportunity in Lever.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
[Rest API] Create a new candidate opportunity
Create a new candidate opportunity (the primary write action in Lever's pipeline).
Each record from your Nexset is sent as a JSON request body to create a new opportunity in Lever.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
[Rest API] Create a new job posting
Create a new job posting in Lever.
Each record from your Nexset is sent as a JSON request body to create a new posting in Lever.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
[Rest API] Update opportunity stage
Advance or change the pipeline stage of a candidate opportunity.
This endpoint requires an Opportunity ID identifying the opportunity to update. Each record is sent as a JSON request body.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
[Rest API] Add note to opportunity
Add a recruiter or system note to a candidate opportunity.
This endpoint requires an Opportunity ID identifying the opportunity to update. Each record is sent as a JSON request body.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
[Rest API] Update job posting
Update an existing job posting (change status, content, owner, etc.).
This endpoint requires a Posting ID identifying the posting to update. Each record is sent as a JSON request body.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
[Rest API] Create referral
Create an employee referral for a candidate opportunity.
This endpoint requires an Opportunity ID identifying the opportunity to update. Each record is sent as a JSON request body.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
[Rest API] Create offer
Create an offer for a candidate opportunity.
This endpoint requires an Opportunity ID identifying the opportunity to update. Each record is sent as a JSON request body.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
[Rest API] Archive opportunity
Archive (or unarchive) a candidate opportunity with a specified reason (hired / rejected).
This endpoint requires an Opportunity ID identifying the opportunity to update. Each record is sent as a JSON request body.
The request body must match Lever's expected format. For details on required fields and request structure, see the Lever Developer Documentation.
Lever Hiring destinations can also be manually configured to send data to any valid Lever Data API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Lever endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Lever endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
