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

# Fanvue webhooks overview

> Receive real-time Fanvue events by webhook instead of polling. Pick the creator or checkout event family, verify each signed HTTP POST delivery.

Webhooks let your app receive live notifications of activity on your users' accounts instead of polling the API. Every delivery is an HTTP `POST` you verify with a signature.

Pick the event family that matches your integration, or see every event across all families in one table in the [Event Catalog](/docs/webhooks/event-catalog):

<CardGroup cols={2}>
  <Card title="Creator events" icon="user" href="/docs/creator/overview">
    The current platform events for a creator's whole account: payments, subscriptions, messages, engagement, refunds, disputes, and fan mute/presence. One Standard-Webhooks envelope. **Start here.**
  </Card>

  <Card title="Checkout events" icon="cart-shopping" href="/docs/checkout/overview">
    Commercial activity on a creator's checkout links: payments, memberships, refunds, disputes, and payouts.
  </Card>

  <Card title="App webhooks" icon="puzzle-piece" href="/docs/app-store/webhooks">
    Your app's own sales, purchases, subscriptions, refunds, disputes (`app.*`), gated on `read:self`.
  </Card>

  <Card title="Legacy events (deprecated)" icon="triangle-exclamation" href="/docs/webhooks/webhooks-overview">
    The original flat platform events (`purchase.new`, `message.received`, …). **Deprecated**, kept for existing integrations. New integrations should use Creator events.
  </Card>
</CardGroup>

<Note>
  New to Fanvue webhooks? Use **Creator events**, they replace the legacy flat events with richer payloads and a single consistent envelope. See [Migrating from the legacy events](/docs/creator/overview#migrating-from-the-legacy-events).
</Note>

## Verifying deliveries

Every webhook request includes an `X-Fanvue-Signature` header. Verify it on every request so forged or replayed events are rejected before you act on them. This is the same across all event families, see [Verify Webhook Signatures](/docs/webhooks/signature-verification).

## Setting up

Add an endpoint and select the events you want in the Fanvue Developer Area (**your app → Events** tab). A single endpoint can receive events from multiple families; each event is delivered only if your subscription includes it. Each event requires specific OAuth scopes, the reference page for each family lists them.