Connect Lever

Request checks from Lever stages and get each check's status back as a note. Reports stay in PreHireBadge.

Updated 8 of 17 in API, MCP and integrations

Works with Lever. This connection is in beta. When a candidate reaches a stage you choose, PreHireBadge creates a check request in Ready to send. A person on your team confirms and sends it. When the check is complete, Lever gets a status note on the opportunity. Reports, results, and AI summaries stay in PreHireBadge.

Who it is for. An owner or admin who uses Lever to manage candidates and wants check requests to start from the hiring pipeline without switching tools.

How to connect

  1. In Lever, open Settings, then Integrations and API, then API credentials. Create a key for PreHireBadge with permission for opportunities, stages, archive reasons, postings, and notes.
  2. In PreHireBadge, open Settings, then Integrations, find Lever, and choose Connect. Paste the key, then accept the integration certification.
  3. Pick the stages that should request a check, your default work location, and the default pay band.
The Lever setup page, where you paste your API key.
The Lever setup page, where you paste your API key.

What Lever receives

PreHireBadge adds a status note to the opportunity in Lever. It does not notify the followers on the opportunity. The note looks like this:

PreHireBadge background check: Clear. Updated Nov 11, 2026. Check 0B6F2B1E. Sign in to view: …

Lever never receives the report, results, AI summaries, or resumes. Rejected and hired statuses come straight from Lever; PreHireBadge reads them to run the adverse action watchdog. In Lever, hired means the opportunity is archived with a reason of type Hired.

No instant updates: the five-minute check

Lever does not send instant updates to PreHireBadge. A background check runs every five minutes, so a stage change, a rejection, or a hire shows up within about five minutes.

A person sends every check

The stage trigger does not order a check and does not use a credit. Open Ready to send, under Screening, confirm the permissible purpose, and send it there.

When something fails

Settings, then Integrations, lists each connected app. The Activity card shows recent requests. Each error includes a short fix. Common problems:

  • The hiring tool did not accept the saved key. The key may have been deleted or may be missing one of the permissions above. Create a new key in Lever if needed, then Disconnect and connect again with the new key.
  • The hiring tool refused a request. A stage you chose may have been renamed or removed in Lever. Reselect the stages in the Setup section on the integration page.

Disconnect there to stop the integration. Requests already waiting in Ready to send can still be dismissed.

See Integrations and the FCRA and adverse action watchdog for more on how connected hiring tools work with PreHireBadge.

Was this article helpful?