Enabling and using the SpringVerify integration

Available for Roles Super Admin, Admin, Team Member, Limited Team Member
Can only be configured by Super Admins
Permissions • To enable: Manage API credentials and manage integrations
• To use: Manage profiles and view associated postings
Packages LeverTRM, LeverTRM for Enterprise

The SpringVerify integration allows you to send candidates' from Lever to SpringVerify in order to run a background checks. This integration is designed to incorporate the background check process seamlessly into your recruitment workflow in Lever.

Setting up the SpringVerify integration


You must be a team or organization with admin rights in SpringVerify to install this integration.
  • In SpringVerify, navigate to the Integrations page
  • Click Connect on the Lever Integration Card

Lever integration card in SpringVerify

  • Click Connect on the Lever integration page to log into Lever

Lever integration page in SpringVerify

  • On the modal, log into Lever
  • Review list of requested permissions; click Accept.

Two frames. Left frame: Lever login modal. Right frame: App authorization modal with listed permissions

  • You will be redirected back to SpringVerify to complete the initial background check integration configuration

Configuring the SpringVerify integration

  • Select the stage from which the candidate will be retrieved from Lever to SpringVerify (e.g. Offer Accepted)


If you want the candidate exported when marked as 'Hired', you can leave this field as 'Select Stage'.

Lever integration page in SpringVerify; selected stage is Offer_Accepted

  • Next, configure the background check package to be applied to a candidate by mapping the appropriate tag from Lever (e.g. Fresher)


Each candidate on a Lever must be assigned a tag in order for the integration to select the correct package. If a candidate is detected without a tag or unmapped tags, that candidate will not be added to SpringVerify.

Lever integration page in SpringVerify; selected stage is Offer_Accepted and associated package tags are listed

  • Click the Save button

SpringVerify’s suggestions on setting up tags in Lever
Instead of having to add a tag to every candidate, which can sometimes lead to the user forgetting to add the tag, it is recommended to add the relevant tag to the job opportunity. This will ensure that every candidate applying for an opportunity will automatically have the relevant tag added to their profile without having to add it manually.

Need to set a default package for all candidates without using a tag?
If you use only one package variant for all your candidates and do not want to have to add a tag for every candidate, contact cs@springverify.com

Using the SpringVerify integration

How does the integration work?
SpringVerify will check Lever every 15 minutes to identify new candidates that are in the stage configured by you. If candidates are found with the following mandatory information, they will be added to SpringVerify. 

  • Name
  • Email
  • Phone
  • Tag (to select the correct package on SpringVerify)

Potential issues with the integration and how to handle them
In the event something goes wrong, SpringVerify Admins will receive an email detailing the problem. Please find below a few common issues: 

  1. Candidates without the required information
    • Fix by ensuring every candidate include the required information on Lever
    • Re-add these candidate manually on SpringVerify
  2. Candidate with unmapped tags or no tags
    • Fix by ensuring every candidate has the correct tag
  3. Authentication Issue
  4. Stage not found
    • The stage configured is no longer available as it might have been deleted on Lever. Fix by visiting SpringVerify and updating the stage with the new stage

To learn more, reach out to cs@springverify.com

Disabling the SpringVerify integration

  1. In Lever navigate to Settings > Integrations and API
  2. Under the Authorized Apps tab, locate the SpringVerify app
  3. Click Revoke access to disable the integration
Was this article helpful?
0 out of 0 found this helpful