Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: 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.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
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 (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.

​
Provider notes

  • The authorize request must include audience=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.

​
Tools

​
Verify the connection

Call a read tool such as lever__list_opportunities with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.