Access Token

Connect to sandbox instance?

Refresh Token

Lever

_objects

Datetime when application was last archived in Lever.

Reason why application was last archived.

Any additional comments from candidate included in job application

Candidate's current company or organization

Contact UID associated with an application.

Datetime when application was created in Lever

An array of customized forms. If the application is of type referral, the custom questions will include a referral form. If the application is type posting, the custom questions include customized posting forms.

List of candidate links (e.g. personal website, LinkedIn profile, etc.)

Opportunity profile associated with an application.

The hiring manager of the job posting at the time when the candidate applies to that job.

The owner of the job posting at the time when the candidate applies to that job.

If the application was archived as hired against a requisition, this is the data related to the requisition.

An application can be of type referral, user, or posting. Applications of type referral are created when a user refers a candidate for a job posting. Applications have type user when they are applied manually to a posting in Lever. Applications have type posting when a candidate applies to a job posting through your company's jobs page.

If the application is of type referral, this is the user who made the referral.

Applications

Emails that the contact can be reached at

Contact headline, typically a list of previous companies where the contact has worked or schools that the contact has attended

Indicates whether a contact has been anonymized. Anonymized contacts have their personal information removed. Non-personal metadata may remain for accurate reporting purposes.

A single line description of the location

Contacts

Datetime when interview was canceled. Value is null if interview was never canceled

Datetime when interview is scheduled to occur

The feedback forms associated with this interview

Frequency of feedback reminders (i.e. once, daily, frequently, none). Defaults to 'frequently' which is every 6 hours

The feedback form template selected for this interview

Interview location. Usually the name of a booked conference room but can also be a phone number to call

List of job postings that the interview is associated with

The stage in which the candidate resided when this interview was scheduled

Interviews

An array of form fields. Notes only support the note field type.

Whether or not this note has been made secret.

Form title. This can be edited in Feedback and Form Settings.

The user who began the note thread on the candidate's profile

Notes

Offers

An array, containing up to one Application ID (can be either an active or archived Application). Each Opportunity can only have up to one application

Datetime when Opportunity was archived in Lever

The confidentiality of the opportunity. An opportunity can only be confidential if it is associated with a confidential job posting. Learn more about confidential data in the API. Can be one of the following values: non-confidential, confidential.

Datetime when this Opportunity was created in Lever. For candidates who applied to a job posting on your website, the date and time when the Opportunity was created in Lever is the moment when the candidate clicked the "Apply" button on their application

An object containing a candidate's data protection status based on candidate-provided consent and applicable data policy regulations. If there is no policy in place or if no policies apply to the candidate, value is null. (shared by contact)

An object representing the consent status for a specified processing activity (one of store or contact)

Timestamp for when the Opportunity was deleted. Note that this attribute only appears for deleted Opportunities

User ID of the user who deleted the Opportunity. Note that this attribute only appears for deleted Opportunities

An array of user IDs of the followers of this Opportunity

Indicates whether an Opportunity has been anonymized. When all of a contact’s Opportunities have been anonymized, the contact is fully anonymized and their personal information is removed. Non-personal metadata may remain for accurate reporting purposes

Datetime when the candidate advanced to the pipeline stage where they are currently located in your hiring process for this Opportunity

Datetime when the last interaction with this Opportunity profile occurred

List of Contact links (e.g. personal website, LinkedIn profile, etc.)

The way this Opportunity was added to Lever. Can be one of the following values: agency, applied, internal, referred, sourced, university

User an opportunity is being created or updated on behalf of

If this Opportunity is snoozed, the timestamp will reflect the datetime when the snooze period ends

An array of source strings for this Opportunity

Stage UID of this Opportunity's current stage

An array of historical stage changes for this Opportunity

Datetime when this Opportunity was updated in Lever

URL that points to the account's list of candidates

URL that points to the candidate's profile page for this Opportunity

Opportunities

Closing statement on job posting, as plaintext.

Closing statement on job posting, as styled HTML.

Custom closing statement on a job posting, as styled HTML. The final closingHtml on a posting is the closingPostingHtml with any closing template HTML applicable to this posting appended to the end. Supported tags, attributes, and styles are listed under HTML support for DESCRIPTION HTML. Learn more about openers and closers here.

Tag for job posting work type (e.g. Full-time, Part-time, Internship)

The confidentiality of the posting. It is not possible to update a posting’s confidentiality. Can be one of the following values: non-confidential, confidential.

Datetime when posting was created in Lever

Tag for the department to which the job posting's team belongs, if present

Job posting description that is shown at the top of the jobs pagem, as plaintext.

Job posting description that is shown at the top of the jobs page. Supported tags, attributes, and styles are listed under HTML support for DESCRIPTION HTML.

Job sites that a published posting appears on. If none is provided, distributionChannels defaults to public and internal

An array of user IDs of the followers of this posting.

The user ID of the hiring manager for the job posting.

Deprecated but currently maintained for backward compatibility. Tag for job posting level (e.g. Senior, Junior).

Lists of requirements, responsibilities, etc. that have been added to this posting

The user ID of the posting owner. The posting owner is the individual who is directly responsible for managing all candidates who are applied to that role. If no ID is provided, the posting owner defaults to perform_as

Requisition code associated with this posting. WARNING: This field is deprecated but maintained for backward compatibility. Use the requisitionCodes field instead.

Array of requisition codes associated with this posting

Posting's current status. Valid states are listed here. If none is provided, state defaults to draft

Tag for the team to which the job posting belongs (e.g. Sales, Engineering)

An object containing the list, show and apply urls for the job posting.

The user ID of the user who created the posting.

Workplace type of this posting. Defaults to 'unspecified'. Can be one of the following values: onsite, remote, hybrid

Postings

Datetime when resume was created in Lever. For candidates who applied to a job posting on your website, the date and time when the candidate's resume was created in Lever is the moment when the candidate clicked the "Attach Resume/CV" button on their application.

An object containing resume file metadata and download url.

The status of processing the file. Can be one of the following values: processing, processed, unsupported, error, or null.

The candidate's parsed resume, usually extracted from an attached PDF/Word document or online profile (LinkedIn, GitHub, AngelList, etc).

Resumes

Number of candidates tagged with this source

Sources

Stages

Users

Retrieve Single Application

Retrieve Applications

Retrieve Single Reason

Retrieve Reasons

Retrieve Audit Events

Get Contact

Update Contact

Only available on interview feedback at the moment.

Create Feedback

Retrieve All Feedback

Delete Feedback

Retrieve Single Feedback

Update Feedback

Create Feedback Template

Retrieve Feedback Templates

Delete Feedback Template

Retrieve Single Feedback Template

Update Feedback Template

Upload Single File

Create Form Template

Retrieve Form Templates

Delete Form Template

Retrieve Single Form Template

Update Form Template

Retrieve Single Interview

Update Interview

Delete Interview

Retrieve Interviews

Create Interview

Retrieve Single Note

Retrieve Notes

Create Note

Delete Note

Retrieve Offers

Download Offer File

Create Opportunity

Retrieve Opportunities Copy

Retrieve Single Opportunity

Retrieve Single Panel

Update Panel

Delete Panel

Retrieve Panels

Create Panel

Retrieve Single Posting

Update Posting

Retrieve Postings

Create Posting

Retrieve Single Referral

Retrieve Referrals

Create Requisition

Get Requisitions

Update Requisition

Create Field

Update Field

Delete Custom Field

Append Options

Update Options

Delete Options

Download Resume File

Retrieve Sources

Retrieve Single Stage

Retrieve Stages

Retrieve Tags

Upload File

Retrieve Users

Create Webhook

Find and list webhooks associated with the api key or bearer token used in the request.

List Webhooks

Update Webhooks

Delete Webhook

Microsoft Sharepoint

Salesforce

HubSpot

Zoho CRM

Microsoft Dynamics 365

Pipedrive

Monday

Slack

Attio

Jira

Xero

Freshsales

Keap

Notion

Asana

BambooHR

SugarCRM

Github

Outreach

ActiveCampaign

Capsule CRM

Salesloft

Clickup

Zendesk

Microsoft Teams

Zoho Books

Agile CRM

SalesForce Pardot

SharpSpring

Teamleader

Insightly

Calendly

Copper

Greenhouse Harvest

Trello Connector

Close

# Continuous Import of Users to Your App

This scenario enables your application to continuously sync Users from any external application to your app's API. It handles the initial import of Users and keeps them synchronized when a User is created, updated, or deleted in the external application.

When receiving Users data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Users to my App

Import Users and receive created/updated or deleted events

Lever API Integration Profile

Data Collections

Operations

Integration Scenarios

Continuously Import Users to my App

Continuously Import Job Offers to my App

Create Job Interview

Continuously Import Job Candidates to my App

Update Job Application

Two-way realtime sync of Job Offers

Similar Integrations

Build every single integration your customers need with AI