Lever OAuth 2.0 connector profile – StackOne setup guide

Start by expressing interest in building a product integration with Lever through their Partner Program.

• Navigate to the Lever Partner page and submit an application to become a partner.
• Once approved, the Lever team will provide you with a Lever sandbox account for development.
• You’ll receive login credentials for your sandbox environment.

After receiving your sandbox account, you’ll need to register your OAuth application to receive Client ID and Client Secret credentials.

• Navigate to the OAuth Registration Form provided in the Lever OAuth documentation.
• Review the OAuth requirements and documentation before proceeding with registration.

Fill out the OAuth application registration form with the required information about your integration.

• Integration Name - Enter your company name or the name of the product being connected to Lever.
• Integration Description - Provide a description between 20 and 140 characters. This will be displayed in the Lever integration ecosystem.
• Callback URL - Enter https://api.stackone.com/connect/oauth2/lever/callback as the redirect URI.
• Square Logo URL - Provide a direct link to your square logo (150x150px recommended).
• Required Scopes - Select the OAuth scopes your integration needs (typically 5-8 scopes, maximum 20). Write scopes include all corresponding read permissions.

After submitting the registration form, the Lever team will review your application and create your OAuth app.

• Click Submit to send your registration.
• The Lever team will create your OAuth application and send you the Client ID and Client Secret. Store both credentials securely for use later.
• After completing development and QA review, you’ll receive production credentials for https://api.lever.co/v1/.

The sandbox environment is used for development and testing without affecting live data.

• Base URL - https://api.sandbox.lever.co/v1
• Use Case - Development, testing, and QA validation

The production environment is used for live integrations with real candidate data.

• Base URL - https://api.lever.co/v1
• Use Case - Live production integrations

Lever scopes are organized by resource type and access level.

• Read scopes - Allow viewing data (e.g., opportunities:read:admin)
• Write scopes - Allow viewing and managing data, includes corresponding read permissions (e.g., opportunities:write:admin includes opportunities:read:admin)
• offline_access - Required scope to receive a refresh token for maintaining persistent authentication

If no custom scopes are specified during StackOne configuration, the integration will use a comprehensive set of default scopes.

Note: Both offline_access and users:read:admin scopes must be included when configuring custom scopes.