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

# Lever OAuth 2.0 connector profile – StackOne setup guide

> Set up the OAuth 2.0 connector profile for Lever in StackOne. One-time admin setup required before your users can link Lever accounts via Hub.

<Warning>Admin privileges within Lever are required. You must register as a Lever Partner and receive OAuth credentials from the Lever team before you can authenticate.</Warning>

<section data-guide-section data-guide-scopes="">
  <h2>Register OAuth Application with Lever</h2>

  <p>To connect Lever with StackOne, you need to register your application through Lever's Partner Program. This process involves becoming a partner, registering for OAuth, and receiving credentials from the Lever team.</p>

  <Steps>
    <Step title="Become a Lever Partner">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Start by expressing interest in building a product integration with Lever through their <a href="https://hire.sandbox.lever.co/developer/partner" target="_blank" rel="noopener noreferrer">Partner Program</a>.</p>

        <ul>
          <li>Navigate to the Lever Partner page and submit an application to <a href="https://www.lever.co/partnershipinterest/" target="_blank" rel="noopener noreferrer">become a partner</a>.</li>
          <li>Once approved, the Lever team will provide you with a Lever sandbox account for development.</li>
          <li>You'll receive login credentials for your sandbox environment.</li>
        </ul>
      </div>
    </Step>

    <Step title="Access OAuth Registration Form">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>After receiving your sandbox account, you'll need to register your OAuth application to receive Client ID and Client Secret credentials.</p>

        <ul>
          <li>Navigate to the <a href="https://hire.sandbox.lever.co/settings/integrations?tab=oauth" target="_blank" rel="noopener noreferrer">OAuth Registration Form</a> provided in the <a href="https://hire.sandbox.lever.co/developer/oauth" target="_blank" rel="noopener noreferrer">Lever OAuth documentation</a>.</li>
          <li>Review the OAuth requirements and documentation before proceeding with registration.</li>
        </ul>
      </div>
    </Step>

    <Step title="Complete Registration Form">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Fill out the OAuth application registration form with the required information about your integration.</p>

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

    <Step title="Submit and Wait for Credentials">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>After submitting the registration form, the Lever team will review your application and create your OAuth app.</p>

        <ul>
          <li>Click <strong>Submit</strong> to send your registration.</li>
          <li>The Lever team will create your OAuth application and send you the <strong>Client ID</strong> and <strong>Client Secret</strong>. Store both credentials securely for use later.</li>
          <li>After completing development and QA review, you'll receive production credentials for <strong>[https://api.lever.co/v1/](https://api.lever.co/v1/)</strong>.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Understanding Environments</h2>

  <p>Lever provides separate sandbox and production environments for development and live operations.</p>

  <Steps>
    <Step title="Sandbox Environment">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>The sandbox environment is used for development and testing without affecting live data.</p>

        <ul>
          <li><strong>Base URL</strong> - `https://api.sandbox.lever.co/v1`</li>
          <li><strong>Use Case</strong> - Development, testing, and QA validation</li>
        </ul>
      </div>
    </Step>

    <Step title="Production Environment">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>The production environment is used for live integrations with real candidate data.</p>

        <ul>
          <li><strong>Base URL</strong> - `https://api.lever.co/v1`</li>
          <li><strong>Use Case</strong> - Live production integrations</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Understanding OAuth Scopes</h2>

  <p>Lever OAuth scopes control what data and operations your application can access.</p>

  <Steps>
    <Step title="Scope Structure">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Lever scopes are organized by resource type and access level.</p>

        <ul>
          <li><strong>Read scopes</strong> - Allow viewing data (e.g., opportunities:read:admin)</li>
          <li><strong>Write scopes</strong> - Allow viewing and managing data, includes corresponding read permissions (e.g., opportunities:write:admin includes opportunities:read:admin)</li>
          <li><strong>offline\_access</strong> - Required scope to receive a refresh token for maintaining persistent authentication</li>
        </ul>
      </div>
    </Step>

    <Step title="Default Scopes">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>If no custom scopes are specified during StackOne configuration, the integration will use a comprehensive set of default scopes.</p>
      </div>
    </Step>

    <Step title="Required Scopes for Custom Configuration">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p><strong>Note:</strong> Both `offline_access` and `users:read:admin` scopes must be included when configuring custom scopes.</p>
      </div>
    </Step>
  </Steps>
</section>

## Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for <strong>Lever</strong>:

<Steps>
  <Step title="Navigate to Connector Profiles">
    Login to StackOne and navigate to [Connector Profiles](https://app.stackone.com/connector_profiles)
  </Step>

  <Step title="Create New Connector Profile">
    <ul>
      <li>Click <strong>+ Connector Profile</strong></li>
      <li>Search for and select <strong>Lever</strong></li>
      <li>Select <strong>Type</strong> as <strong>OAuth 2.0</strong></li>

      <li>
        Fill out the fields using details retrieved from your provider:

        <ul style={{ marginLeft: '20px' }}>
          <li><strong>Client ID</strong></li>
          <li><strong>Client Secret</strong></li>
          <li><strong>Application Scopes</strong> (Optional)</li>
        </ul>
      </li>

      <li>(Optional) Select <strong>Actions</strong> to be enabled for this Connector Profile</li>
      <li>Click <strong>Create profile</strong></li>
    </ul>
  </Step>
</Steps>

Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to <a href="/guides/accounts-section#linking-accounts">Link Accounts</a> for <strong>Lever</strong>.