Skip to main content
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:

Creator events

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.

Checkout events

Commercial activity on a creator’s checkout links: payments, memberships, refunds, disputes, and payouts.

App webhooks

Your app’s own sales, purchases, subscriptions, refunds, disputes (app.*), gated on read:self.

Legacy events (deprecated)

The original flat platform events (purchase.new, message.received, …). Deprecated, kept for existing integrations. New integrations should use Creator events.
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.

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

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