> ## 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.

# Ashby Webhook Setup Guide

> Configure Ashby to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](https://docs.stackone.com/connectors/ashby.md#getting-started) on the Ashby connector page.

## How Ashby webhooks are set up

There is nothing to paste into Ashby and no URL to copy. For each event you enable in StackOne, StackOne creates an Ashby webhook for it and removes it again when the account is disconnected.

<ul>
  <li>Ashby takes one **Webhook Type** per webhook, so each enabled event becomes its own webhook in Ashby.</li>
  <li>You can review the webhooks StackOne created in Ashby under **Admin** > **Integrations** > **Webhooks**. Don't edit or delete them there. Manage events in StackOne instead.</li>
</ul>

## Before you enable events

Webhooks are created with the API key on this connection, so the key must be allowed to manage them.

<ul>
  <li>Give the API key write access to the **API Keys** module. Ashby lists webhook create, update and delete under that module.</li>
  <li>Give the key read access to the modules whose data you want events for, such as candidates, jobs, interviews and offers.</li>
  <li>Events for features your organization doesn't use, such as an HRIS integration, e-signature or take-home assignments, are only sent once that feature is set up in Ashby.</li>
</ul>

## Available webhook events

The following Ashby events can be enabled. Only events selected in StackOne get a webhook in Ashby, and Ashby doesn't send events it has no webhook for.

**1. Ping**

Handled automatically whenever any other event is enabled.

<ul>
  <li>**Active Check** (`ping`) — Fired when a webhook is created or edited, to check the URL is live. Ashby disables a webhook whose ping isn't answered.</li>
</ul>

**2. Application events**

Events on candidate applications, from submission to hire.

<ul>
  <li>**Application Submitted** (`applicationSubmit`) — Fired when a candidate submits an application or is added to a job manually. Bulk imports and integration syncs do not fire it</li>
  <li>**Application Updated** (`applicationUpdate`) — Fired when an application changes, such as its source, custom fields or a transfer to another job. Stage changes and hires also fire it</li>
  <li>**Candidate Stage Changed** (`candidateStageChange`) — Fired when an application moves to another interview stage. Hires also fire it</li>
  <li>**Candidate Hired** (`candidateHire`) — Fired when a candidate is hired, including on confidential jobs. The payload carries the application and the most recent accepted offer</li>
  <li>**Candidate Pushed to HRIS** (`pushToHRIS`) — Fired when a hired candidate is pushed to the connected HRIS</li>
</ul>

**3. Candidate events**

Events on candidate records and surveys.

<ul>
  <li>**Candidate Deleted** (`candidateDelete`) — Fired when a candidate is deleted. The payload carries only the deleted candidate's id</li>
  <li>**Candidate Merged** (`candidateMerge`) — Fired when two candidates are merged. The payload carries the id of the deleted candidate and of the candidate it was merged into</li>
  <li>**Candidate Recent Email Messages Updated** (`candidateRecentEmailMessagesUpdated`) — Fired when a candidate's recent email messages change. Beta in Ashby and not available to every organization</li>
  <li>**Survey Submitted** (`surveySubmit`) — Fired when a candidate submits a non-anonymous survey</li>
</ul>

**4. Interview events**

Events on interview plans, schedules and take-home assignments.

<ul>
  <li>**Interview Plan Transitioned** (`interviewPlanTransition`) — Fired when a job switches to a different interview plan. The payload carries both plans and the stage mappings. It also fires the job updated event</li>
  <li>**Interview Schedule Created** (`interviewScheduleCreate`) — Fired when an interview schedule is created. It also fires the interview schedule updated event</li>
  <li>**Interview Schedule Updated** (`interviewScheduleUpdate`) — Fired when an interview schedule changes, including when its interviews are scheduled, updated or canceled</li>
  <li>**Take Home Assignment Assigned** (`takeHomeAssignmentAssigned`) — Fired when a take-home assignment is assigned to a candidate</li>
  <li>**Take Home Assignment Submitted** (`takeHomeAssignmentSubmitted`) — Fired when a candidate submits a take-home assignment</li>
  <li>**Take Home Assignment Completed** (`takeHomeAssignmentCompleted`) — Fired when a take-home assignment is marked completed</li>
  <li>**Take Home Assignment Cancelled** (`takeHomeAssignmentCancelled`) — Fired when a take-home assignment is canceled</li>
</ul>

**5. Job, job posting and opening events**

Events on jobs, their postings and openings.

<ul>
  <li>**Job Created** (`jobCreate`) — Fired when a job is created</li>
  <li>**Job Updated** (`jobUpdate`) — Fired when a job changes. An interview plan transition also fires it</li>
  <li>**Job Posting Published** (`jobPostingPublish`) — Fired when a job posting is published. It also fires the job posting updated event</li>
  <li>**Job Posting Updated** (`jobPostingUpdate`) — Fired when a job posting changes, including when it is published or unpublished</li>
  <li>**Job Posting Unpublished** (`jobPostingUnpublish`) — Fired when a job posting is unpublished. It also fires the job posting updated event</li>
  <li>**Job Posting Deleted** (`jobPostingDelete`) — Fired when a job posting is deleted. The payload carries the posting id and its job id</li>
  <li>**Opening Created** (`openingCreate`) — Fired when a job opening is created</li>
  <li>**Opening Updated** (`openingUpdate`) — Fired when a job opening changes</li>
  <li>**Opening Deleted** (`openingDelete`) — Fired when a job opening is deleted</li>
</ul>

**6. Offer events**

Events on offers and their e-signature requests.

<ul>
  <li>**Offer Created** (`offerCreate`) — Fired when a new offer process is created for a candidate</li>
  <li>**Offer Updated** (`offerUpdate`) — Fired when an offer changes</li>
  <li>**Offer Deleted** (`offerDelete`) — Fired when an offer process is deleted. The payload carries only the offer id</li>
  <li>**Signature Request Updated** (`signatureRequestUpdate`) — Fired when an e-signature request on an application or offer is sent, canceled, completed or deleted (data.eventType)</li>
</ul>

## 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.