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

# Set up webhooks

> Choose events and tell OFAuth where to send webhook requests.

Add your receiver's public HTTPS URL to OFAuth. A receiver is a route in your app that accepts webhook requests. To test a receiver running on your computer, expose it with a [Cloudflare Quick Tunnel](https://docs.ofauth.com/v3/guides/webhooks-local.md).

## Choose what to receive

| Your application needs to… | Use |
| - | - |
| Pause work when an account expires, or remove access when authorization ends | [Lifecycle webhooks](https://docs.ofauth.com/v3/api-reference/system-webhook-events.md) |
| Receive messages, likes, post updates, and other supported account activity | [OnlyFans activity events](https://docs.ofauth.com/v3/guides/realtime-onlyfans-events.md) through webhooks |
| Stream OnlyFans activity to your server or a web page | [Realtime stream](https://docs.ofauth.com/v3/guides/realtime-onlyfans-events.md#receive-realtime-over-server-sent-events) |

You can use lifecycle and activity events together. Lifecycle events report changes to account access. OFAuth sends them only through webhooks.

## Before you start

[Create your integration](https://docs.ofauth.com/v3/setup/create-integration.md) and choose the environment to test. Your receiver must check each request's signature using Standard Webhooks. Use the original request body for this check. During setup, the receiver must also return the signed challenge text sent by OFAuth. Use the [receiver implementation](https://docs.ofauth.com/v3/guides/webhook-handler.md#run-the-receiver) if you need that code.

## Add a destination

1. Open your External Integration in the OFAuth dashboard.
2. Choose Sandbox, Test, or Live.
3. Open **Webhooks**.
4. Select **Create webhook**.
5. Enter the receiver's HTTPS URL under **Endpoint URL**.
6. Select **Send Realtime events**, **Send lifecycle events**, or both.
7. Save the destination's signing secret in your backend's secret storage. OFAuth shows it only once.
8. Configure the receiver with this secret.
9. Select **Verify** for the pending destination. OFAuth sends a signed challenge. After checking the signature, your receiver returns the exact challenge text. See the [receiver example](https://docs.ofauth.com/v3/guides/webhook-handler.md#verify-destination-ownership).
10. Confirm that the destination is **Verified** and **Active**. If it is disabled, select **Enable**.

![The Sandbox Create webhook form showing Endpoint URL, Send Realtime events, Send lifecycle events, and the Create webhook button. The form has not been submitted.](https://mintcdn.com/ofauth/VVqOdSxbrh7mDF0M/images/v3/setup-webhook-destination.png?fit=max\&auto=format\&n=VVqOdSxbrh7mDF0M\&q=85\&s=fe788bcbad88a91d9edddc6fff29315c)

Each destination has its own secret. Environments do not share destinations or events. Lifecycle deliveries are not billed.

Verification succeeds when your receiver echoes the signed challenge as plain text. Normal events then use the [event envelope](https://docs.ofauth.com/v3/api-reference/webhooks.md#envelope), including `eventId` and `type`. The challenge has no `eventId`.

## Next step

Once the destination is **Verified** and **Active**, add [event storage and duplicate checks](https://docs.ofauth.com/v3/guides/webhook-handler.md#apply-events-to-your-application) before applying customer updates. Use the [delivery reference](https://docs.ofauth.com/v3/api-reference/webhooks.md) for event fields and event order.


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