> ## Documentation Index
> Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Lever

> Read opportunities, postings, and stages from the Lever ATS

## At a glance

* **Availability**: Experimental ([how to enable](/cloud/integrations)).
* **Auth**: OAuth 2.0.
* **Connection**: A user authorizes the connection in the provider's consent screen.
* **Scopes**: `opportunities:read:admin`, `postings:read:admin`, `stages:read:admin`, `offline_access`.
* **Docs**: [https://hire.lever.co/developer/documentation](https://hire.lever.co/developer/documentation)

## Credentials

Set these per environment. See [Connect an integration](/cloud/integrations).

With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.

| Variable              | Required | Description                                                                                     |
| --------------------- | -------- | ----------------------------------------------------------------------------------------------- |
| `LEVER_CLIENT_ID`     | Yes      | Lever OAuth Client ID [Docs](https://hire.lever.co/developer/documentation#authentication).     |
| `LEVER_CLIENT_SECRET` | Yes      | Lever OAuth Client Secret [Docs](https://hire.lever.co/developer/documentation#authentication). |

## Setup

1. **Register an OAuth app with Lever**: Lever OAuth apps are issued through the Lever partner process - request credentials at [https://hire.lever.co/developer/oauth](https://hire.lever.co/developer/oauth) (or via partner support). For quick internal testing, Lever also offers API keys, but this connector uses OAuth.
2. **Use a sandbox environment**: Ask Lever for a sandbox account to test against before touching production hiring data.
3. **Set the redirect URI**: Register your deployment's /api/auth/lever/callback URL as an allowed redirect URI.
4. **Set environment variables**: Add LEVER\_CLIENT\_ID and LEVER\_CLIENT\_SECRET to your .env.
5. **Connect and verify**: Complete the OAuth consent flow as a Lever Super Admin, then run List Stages to confirm access.

* The authorize request must include audience=[https://api.lever.co/v1/](https://api.lever.co/v1/) - the connector sends it automatically
* offline\_access (with prompt=consent) is required to receive a refresh token
* Scopes are granular per resource; add more (e.g. users:read:admin) if you extend the tools

Provider API reference: [https://hire.lever.co/developer/documentation](https://hire.lever.co/developer/documentation)

## Tools

| Tool               | Access | Description                  |
| ------------------ | ------ | ---------------------------- |
| List Opportunities | Read   | List candidate opportunities |
| Get Opportunity    | Read   | Get a single opportunity     |
| List Postings      | Read   | List job postings            |
| Get Posting        | Read   | Get a single job posting     |
| List Stages        | Read   | List pipeline stages         |

## Example prompts

* List my active Lever opportunities grouped by stage with candidate names and tags.
* Show my published Lever postings with their teams and locations.