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

# SearchOS Webhook Setup Guide

> Configure SearchOS 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/searchos.md#getting-started) on the SearchOS connector page.

## Retrieve the Native Webhook URL

The **Native Webhook URL** is generated once the SearchOS account has been linked. SearchOS has no webhook API, so you add it in SearchOS by hand.

**1. Copy the URL**

Open the linked SearchOS account in StackOne, where the **Native Webhook URL** field shows the URL.

<ul>
  <li>Click the copy icon next to **Native Webhook URL**.</li>
  <li>The URL identifies your linked account, so paste it in full into SearchOS.</li>
</ul>

![StackOne linked account form with the copy icon next to the Native Webhook URL highlighted](https://mintcdn.com/stackone-60/XCCn6S74hKoKhOwb/connectors/searchos/images/events-native-webhook-url.png?fit=max\&auto=format\&n=XCCn6S74hKoKhOwb\&q=85\&s=436af51c4e9697f4e81fd951690f7ad8)

## Adding the webhooks in SearchOS

SearchOS sends one event per webhook, so add one webhook for each event you want to receive.

**1. Add a webhook**

Sign in to your [SearchOS account](https://search-os.io/login), then go to **Settings** > **Workspace & team** and scroll to **Developer** > **Webhooks**.

<ul>
  <li>Choose the event in the dropdown, for example **Candidate created**.</li>
  <li>Paste the **Native Webhook URL** into the URL field.</li>
  <li>Click **Add**.</li>
</ul>

![SearchOS Webhooks settings with the event dropdown, URL field and Add button highlighted](https://mintcdn.com/stackone-60/XCCn6S74hKoKhOwb/connectors/searchos/images/events-add-webhook.png?fit=max\&auto=format\&n=XCCn6S74hKoKhOwb\&q=85\&s=c0808ed3f9a88257e0079ee0d595c46f)

**2. Add the other events**

Repeat for each remaining event, pasting the same **Native Webhook URL** each time.

<ul>
  <li>**Careers application received**</li>
  <li>**Offer accepted**</li>
  <li>**Placement made**</li>
</ul>

![SearchOS Webhooks settings with the URL pasted and the Add button highlighted](https://mintcdn.com/stackone-60/XCCn6S74hKoKhOwb/connectors/searchos/images/events-paste-url.png?fit=max\&auto=format\&n=XCCn6S74hKoKhOwb\&q=85\&s=066bd6028c0ecae2293ec6c4a03dbfd0)

**3. Check the webhooks**

Each event you added appears in the **Webhooks** list with its code and URL. To stop an event, click the delete icon on its row.

![SearchOS Webhooks list showing one webhook per event](https://mintcdn.com/stackone-60/XCCn6S74hKoKhOwb/connectors/searchos/images/events-webhook-list.png?fit=max\&auto=format\&n=XCCn6S74hKoKhOwb\&q=85\&s=65c8033933359a513cfe862cd36497ec)

## Available webhook events

The following SearchOS events can be received. Only events you add in SearchOS and enable in StackOne are delivered.

**1. Candidate events**

Events related to candidates and careers-site applications.

<ul>
  <li>**Candidate Created** (`candidate.created`) — Fired when a candidate is added through the app, the API or a CV import</li>
  <li>**Application Received** (`application.received`) — Fired when someone applies on a published vacancy's careers page</li>
</ul>

**2. Pipeline events**

Events related to a vacancy's pipeline.

<ul>
  <li>**Offer Accepted** (`offer.accepted`) — Fired when a pipeline entry's offer status is saved as Accepted</li>
  <li>**Placement Made** (`placement.made`) — Fired when a candidate moves to the Placed stage</li>
</ul>

## Delivery format

Details of how SearchOS delivers events to StackOne.

**1. One event per request**

SearchOS POSTs one JSON event per request, shaped `{ event, firedAt, data }`. Deliveries are not signed, and SearchOS sends no verification request.

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