Use Cases

Become a Lever Partner

We'd love to have you! Get started today by letting us know you are interested. Get more details on building a partner integration on the Partner page.

For an overview of our partner integrations, head over to Lever's ecosystem.

Find the details and suggestions by type of Integration to get you started

Assessments

Assessment integrations invite Opportunity contacts to participate in an assessment based on their stage in Lever

OAuth Scopes

offline_access opportunities:write:admin notes:write:admin stages:read:admin tags:read:admin webhooks:write:admin

optionally: feedback:write:admin and feedback_templates:write:admin or files:write:admin

Webhooks

Candidate Stage Change

Basic Steps

  • The user adds a tag from the list of tags you provide and adds it to their postings
  • Opportunities tied to the posting will inherit the tag.
  • From the Candidate Stage Change webhook, the integration will receive notice of the opportunity moving stages.
  • When the opportunity has moved to the specified stage, using the contact information send the candidate an invitation to an assessment.
  • Update the tags on the opportunity as they progress.
  • Once the candidate has completed the assessment leave a note on the opportunity with a summary.

Expanded Functionality

Add a PDF summary of the assessment as a file or link on the opportunity. Add the results of the assessment as feedback on the opportunity instead of a note.

Relevant Questions on the FAQ Page

How do I add global tags to a Lever account? Can tags be updated? Are stages customized by each company?

FAQ page

Depending on the strategy you have chosen you will also need one of the following: feedback:write:admin and feedback_templates:write:admin, or notes:write:admin and/or files:write:admin

Keep in Mind

Stages are custom to each customer. If you are using a particular stage in your integration, such as CompanyName Assessment, your help center article will need to be clear that the customers must have their stage added to their pipeline.

See example integration

Background Checks

Summary

Your integration will begin when a Lever opportunity stage is changed to background check. The stage change triggers an order in your system, which emails the candidate using the opportunity contact information. As the background check status progressess you will post updates on the opportunity.

Strategies

There are a few solutions that you can utilize to post updates on the progress, and result of the background check: tags, notes, profile forms, and feedback. The most commonly employed is tags. Find questions around the use of tags on our FAQ page

API Key Endpoints

READ: list_opportunities, list_postings, list_stages, read_contact, read_opportunity, read_postings, read_stage

WRITE: update_opportunity_stage

OAuth Scopes

offline_access, opportunities:read:admin, opportunities:write:admin, tags:read:admin, stages:read:admin

Depending on the strategy you have chosen you will also need one of the following: tags:read:admin, notes:read:admin and notes:write:admin, forms:read:admin and forms:write:admin, or feedback_templates:write:admin

Webhooks

Some partners use our webhook candidate stage change to trigger an event on their end. This webhook will trigger on all stage changes and you will need to listen for the correct stage.

Note

Stages are custom to each customer. If you are using a particular stage in your integration, such as Background Check, your help center article will need to be clear that the customers must have their stage added to their pipeline.

See example integration

HRIS & Onboarding

Summary

Your integration will begin when a Lever opportunity is archived with the reason of Hired. The stage change triggers the creation of an employee in your system, using the opportunity's contact and posting information.

API Key Endpoints

READ: read_opportunity, read_archive_reason

OAuth Scopes

offline_access, opportunities:read:admin, archive_reasons:read:admin

Webhooks

Some partners use our webhook candidate archive state change to trigger an event on their end.

See example integration

Job Boards

XML Feed

Job boards can use the customer's XML feed for public postings.

To be published on our list of job boards for customers, let us know where customers should provide their XML feed on our partner interest form (in the description of the integration section).

See the instructions given to customers on how to use their XML feed.

Example XML Feed https://api.lever.co/v0/postings/xmlexample?mode=xml

Example XML Feed Structure

<jobs>
  <job>
    <id><![CDATA[ 4f816f9a-7f03-4e18-9710-6ec9a9c0d40e ]]></id>
    <position><![CDATA[ Software Engineer ]]></position>
    <description
      ><![CDATA[ <div>Description of the job posting</div><div><br
      /></div><div><br></div> ]]></description
    >
    <apply_url
      ><![CDATA[
      https://jobs.lever.co/examplecompany/4f816f9a-7f03-4e18-9710-6ec9a9c0d40e/apply?lever-source=Job%20postings%20feed
      ]]></apply_url
    >
    <employer><![CDATA[ Example Company ]]></employer>
    <location><![CDATA[ Toronto, Ontario ]]></location>
    <category><![CDATA[ Engineering ]]></category>
    <commitment><![CDATA[ Full-Time ]]></commitment>
    <post_date>1568068777313</post_date>
  </job>
<jobs>

Scheduling

Most commonly used API permissions needed

READ

  • Access candidates profile information (name, email, owner, stage, archive state etc.)
  • Access job postings, tags, stages, postings, feedback templates, interviews and applications
  • Access Lever users and their contact info

WRITE

  • Create, update, and delete interviews in Lever

OAuth Scopes

offline_access, opportunities:read:admin, contact:read:admin

See example integration

Sourcing

Sourcing integrations create Opportunities in Lever

Scopes

offline_access opportunities:write:admin postings:read:admin users:read:admin stages:read:admin

optionally: uploads:write:admin

Basic Steps

  • The user selects a candidate to import into Lever and the posting they will be tied to
  • The integration confirms the candidate is not already an opportunity in Lever - (list opportunities with the email parameter)
  • If not a duplicate, the integration creates an opportunity in Lever with the source labeled as the integration name
  • If no posting was selected the candidate becomes a general opportunity
  • The integration confirms import to user

Expanded Functionality

Stages: read the opportunities and the stages to sync the candidates progress through the hiring process

Relevant Questions on the FAQ Page

How to select a user to 'perform-as' when creating an opportunity

See example integration