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

# Setup Webhooks

> Configure your HTTPS endpoint and handle webhook delivery.

Configure a webhook to receive updates from Collective at your organization's HTTPS endpoint. See [Application webhook](https://docs.collective.work/docs/application-webhook.md) for its trigger and payload.

## Activate your webhook

Email [support@collective.work](mailto:support@collective.work) to activate your webhook and configure its URL and bearer token. Include your organization name, recruiter email, and HTTPS endpoint URL.

Collective manages these settings. A bearer token is optional but recommended.

## Receive webhooks

Collective sends a JSON `POST` to your configured URL:

```http theme={null}
Content-Type: application/json
Authorization: Bearer YOUR_WEBHOOK_TOKEN
```

Validate the token on your endpoint. The Authorization header is omitted when no token is configured.

## Responses and retries

Respond within 30 seconds. Redirects are not followed.

| Your response | Collective's behavior |
| - | - |
| Any `2xx` | Delivery accepted. No response body required. |
| `409` | Treated as already received; no retry. |
| `404` or `410` | Delivery stopped for this notification; no retry. |
| Any other status, timeout, or network failure | Delivery retried. |

Collective makes up to 10 total attempts, with retry delays starting at one minute and doubling each time. Repeated deliveries are possible, so make your handler safe to call more than once.


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