Skip to main content
Realtime OnlyFans Events delivers supported translated OnlyFans activity events to your webhook endpoint. Use it when you need low-latency event delivery for product activity instead of connection lifecycle or Dynamic Rules notifications.

​
Quick Reference

​
Configuration

Configure Realtime OnlyFans Events in the OFAuth Dashboard:
  • Set your webhook endpoint URL
  • Set Realtime defaults for new connections in Realtime Config
  • Open Realtime Settings in Connections for each existing connection that should send events
  • Select the realtime payload families for each connection
  • Review delivery history and failures
Changing Realtime settings on an existing connection takes effect after you save the settings. You do not need to reconnect the OnlyFans account. Keep your webhook endpoint reachable and return a 2xx response within 10 seconds. Realtime is available on pay-as-you-go and paid plans. OFAuth meters each delivered realtime webhook event. Review usage and spend limits in the Dashboard.

API Overview

Review the top-level webhook contract and integration notes

System Webhook Events

Connection lifecycle events and Dynamic Rules notifications

​
Event Types

OnlyFans Events are currently in beta. The translated webhook contract is stable, and the documented event categories may expand over time as coverage grows.

​
Payload Format

Realtime OnlyFans Events deliveries share the same top-level envelope:
The data.eventBody object contains the translated OnlyFans event payload. Route deliveries by the top-level type, and parse eventBody defensively because additional event categories may be added over time.

​
Documented Event Schemas

The schema pages below are generated from the same OpenAPI spec as the webhook contract:

​
Delivery & Retries

  • Retry policy: exponential backoff with up to 5 attempts
  • Timeout: 10 seconds per request
  • Ordering: best effort per webhook endpoint
Your endpoint should return a 2xx response within 10 seconds.

​
Signature Verification

Realtime OnlyFans Events uses Svix signing. Every delivery includes these headers:
Verify requests by:
  1. Read the raw request body before parsing JSON.
  2. Pass the raw body, svix-id, svix-timestamp, and svix-signature headers to a Svix webhook verifier.
  3. Use the signing secret from the OFAuth Dashboard.
  4. Use svix-id as the delivery ID for deduplication.
Use the Svix headers only. Do not implement a separate HMAC format. The Svix verifier checks the timestamp and signature for you.

​
Implementation Checklist

  1. Parse the application/json body
  2. Verify the signature before processing
  3. Route the event by type
  4. Return 2xx within 10 seconds
  5. Make handlers idempotent by storing processed svix-id values

​
Troubleshooting

Ensure your endpoint is publicly reachable and returns a 2xx response within 10 seconds.
Verify that the endpoint is active, the connection status is active, Realtime is enabled for that connection, and the required payload family is selected. Saving connection settings does not require a reconnect. Check the delivery history for failures and your organization spend limit.
No. The Dashboard’s example webhook is a synthetic delivery. It verifies your endpoint and signature handling, but it does not represent activity from an OnlyFans account.
Use the raw request body and a Svix webhook verifier. Confirm that the endpoint uses the signing secret shown in the Dashboard and reads the svix-id, svix-timestamp, and svix-signature headers.

​
Next Steps

API Overview

View the top-level Realtime webhook contract

Access API

Use connection IDs to read and write OnlyFans data

System Webhook Events

Connection lifecycle events and Dynamic Rules notifications