> ## 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 Webhook Setup Guide

> Configure Lever to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/lever#getting-started) on the Lever connector page.

<section data-guide-section data-guide-scopes="">
  <h2>Copy the Native Webhook URL from StackOne</h2>

  <p>StackOne generates one webhook URL per connected Lever account. Every event you enable in Lever points at this same URL, and StackOne routes each event to the right handler.</p>

  <Steps>
    <Step title="Copy the URL from the linked account">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>In StackOne Hub, open the linked Lever account and copy the <strong>Native Webhook URL</strong>. The URL already contains the token that identifies your account, so treat it as a secret and do not shorten or edit it.</p>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Open the webhook settings in Lever</h2>

  <p>Webhooks are configured once per Lever environment, under the account's integration settings.</p>

  <Steps>
    <Step title="Sign in to Lever">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Sign in to <a href="https://hire.lever.co" target="_blank" rel="noopener noreferrer">Lever</a> as a Super Admin. Webhook settings are hidden for every other role.</p>
      </div>
    </Step>

    <Step title="Open Integrations and API">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Open <strong>Settings</strong>, then select <strong>Integrations and API</strong> in the left sidebar.</p>

        <img src="https://mintcdn.com/stackone-60/-m_Wkya09ptn4WD9/connectors/lever/images/events-integrations-and-api.png?fit=max&auto=format&n=-m_Wkya09ptn4WD9&q=85&s=3bf001e380ebcd82a70af9ff9f6fa852" alt="The Lever settings sidebar with Integrations and API selected" width="1280" height="800" data-path="connectors/lever/images/events-integrations-and-api.png" />
      </div>
    </Step>

    <Step title="Select the Webhooks tab">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Select the <strong>Webhooks</strong> tab. The <strong>Webhook configuration</strong> section lists every event Lever can send.</p>

        <img src="https://mintcdn.com/stackone-60/-m_Wkya09ptn4WD9/connectors/lever/images/events-webhooks-tab.png?fit=max&auto=format&n=-m_Wkya09ptn4WD9&q=85&s=948e373a03a8f6295ca26e0a398d801d" alt="The Integrations and API page with the Webhooks tab selected" width="1280" height="800" data-path="connectors/lever/images/events-webhooks-tab.png" />
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Add the URL to each event you want</h2>

  <p>Lever keeps a separate URL list for every event. Repeat these steps for each event in the catalog below — enabling an event without adding the URL to it delivers nothing.</p>

  <Steps>
    <Step title="Switch on the event and add the URL">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Switch on the toggle beside the event, for example <strong>Application created</strong>. Select <strong>Add webhook</strong>, then paste the Native Webhook URL into the field. Lever shows the scheme prefix separately, so paste the rest of the URL after it.</p>

        <ul>
          <li>Repeat for every event you want delivered — the URL is stored per event, not per account.</li>
          <li>A webhook StackOne created through the API shows its URL as read-only; Lever does not allow editing those.</li>
        </ul>

        <img src="https://mintcdn.com/stackone-60/-m_Wkya09ptn4WD9/connectors/lever/images/events-add-webhook.png?fit=max&auto=format&n=-m_Wkya09ptn4WD9&q=85&s=55ac58c0011f4b165e92c8d773134401" alt="The Application created event with its toggle, URL field, and Add webhook link" width="1280" height="800" data-path="connectors/lever/images/events-add-webhook.png" />
      </div>
    </Step>

    <Step title="Choose which candidate origins trigger the event">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Expand the event to show <strong>Triggers for candidates of the selected origins:</strong> and tick the origins you want. <strong>Applied</strong>, <strong>Sourced</strong>, <strong>Referred</strong>, <strong>University</strong>, <strong>Internal</strong> and <strong>Agency</strong> are all selected by default. This applies to <strong>Application created</strong>, <strong>Candidate stage change</strong>, <strong>Candidate archive state change</strong> and <strong>Candidate hired</strong> only; the other events always fire.</p>
      </div>
    </Step>

    <Step title="Verify the connection">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Select <strong>Verify connection</strong>. Lever sends a sample request and expects a response within one second. If it reports a failure, select it again — a slow first response is the usual cause, and the second attempt normally succeeds.</p>

        <img src="https://mintcdn.com/stackone-60/-m_Wkya09ptn4WD9/connectors/lever/images/events-verify-connection.png?fit=max&auto=format&n=-m_Wkya09ptn4WD9&q=85&s=0d42c5d5501cede112fcd900ad7d8f01" alt="An expanded event showing the origin triggers, signature token, and the Verify connection button" width="1280" height="800" data-path="connectors/lever/images/events-verify-connection.png" />
      </div>
    </Step>

    <Step title="Note the signature token">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Each event has its own <strong>Signature token</strong>, shown when the event is expanded. Lever signs every request with it so the receiver can confirm the payload came from Lever. <strong>Regenerate Token</strong> issues a new one and invalidates the old.</p>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available webhook events</h2>

  <p>The following Lever events can be enabled. Only events you switch on and give the URL to are delivered — Lever sends nothing for the rest.</p>

  <Steps>
    <Step title="Enable candidate and application events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events covering applications and the candidate lifecycle.</p>

        <ul>
          <li><strong>Application created</strong> (`applicationCreated`) — Fired when a candidate application is created.</li>
          <li><strong>Candidate hired</strong> (`candidateHired`) — Fired when a candidate is marked as hired.</li>
          <li><strong>Candidate stage change</strong> (`candidateStageChange`) — Fired when a candidate moves between stages; carries the stage moved from and to.</li>
          <li><strong>Candidate archive state change</strong> (`candidateArchiveChange`) — Fired when a candidate is archived or unarchived; carries the previous and updated archive state.</li>
          <li><strong>Candidate deleted</strong> (`candidateDeleted`) — Fired when a candidate is deleted; carries the user who deleted them.</li>
        </ul>
      </div>
    </Step>

    <Step title="Enable interview events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events covering interview scheduling. Lever marks these Beta.</p>

        <ul>
          <li><strong>Interview created</strong> (`interviewCreated`) — Fired when an interview is created.</li>
          <li><strong>Interview updated</strong> (`interviewUpdated`) — Fired when an interview is updated.</li>
          <li><strong>Interview deleted</strong> (`interviewDeleted`) — Fired when an interview is deleted.</li>
        </ul>
      </div>
    </Step>

    <Step title="Enable contact events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events covering contact records.</p>

        <ul>
          <li><strong>Contact created</strong> (`contactCreated`) — Fired when a contact is created.</li>
          <li><strong>Contact updated</strong> (`contactUpdated`) — Fired when a contact is updated.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.