Skip to content
Fans API logo, the service that sends these OnlyFans webhooks

Fans API · APIs and developer tools

OnlyFans Webhooks: Events, Payloads, Retries

TL;DR

  • OnlyFans webhooks from Fans API send a POST request to your server when something happens on a connected account, such as a new message, tip, subscriber or sale.
  • You pick the events, add an optional signing secret, and get 34 OnlyFans event types, plus separate Fansly and Fanvue events.
  • Webhooks are part of the Basic and Pro plans and cost 1 credit per 100 events. Skip them if nobody on your team can run a server or a no-code workflow.
Price
Fans API plans: free, $69 or $299/mo
Product
Fans API
Platforms
OnlyFans, Fansly and Fanvue accounts connected to Fans API
Free trial
Free plan exists, but the pricing page lists webhooks only on Basic ($69/month) and Pro ($299/month)

What OnlyFans webhooks are

OnlyFans webhooks from Fans API are HTTP requests that Fans API sends to your server whenever something happens on a connected creator account. A fan sends a message, a tip arrives or a subscription expires, and within moments your endpoint receives a JSON description of it. You don’t have to ask the API every few minutes whether anything changed.

The docs put it simply. Use the API when you need something now and then, like a chat or an earnings report. Use webhooks for the many events you must handle as they happen. Webhooks are part of the OnlyFans API account, not a separate product, and they sit in our APIs and developer tools category. Connected Fansly and Fanvue accounts send their own events, covered on the Fansly API and Fanvue API pages.

Key features of these OnlyFans webhooks

These features come from the Fans API webhooks docs. They cover picking events, receiving them safely and recovering when your endpoint fails.

34 OnlyFans event types

The OnlyFans list has 34 events in 11 groups. The OnlyFans event list shows an example payload for each one. These are the events most agencies start with:

Event Fires when
messages.received A fan sends the creator a message
messages.ppv.unlocked A fan buys a PPV message
tips.received A fan sends a tip
subscriptions.new A new fan subscribes
subscriptions.renewed A fan renews a subscription
subscriptions.expired A fan’s subscription runs out
transactions.new Any payment arrives, up to 3 minutes late
users.online A fan is detected as online
accounts.session_expired The creator’s connection needs attention
data_exports.completed A requested data export is ready

Events about a fan include a fan object with the same fields every time, and many include fanData with that fan’s total spending. The export events pair with the no-code Data exports tool.

Optional signing secret

When you add a webhook you can set a signing secret. Every request then carries a Signature header that proves it came from Fans API. The docs recommend a long, random string for the secret.

Deduplication and replays

Most events carry an X-OFAPI-Idempotency-Key header that stays the same on every attempt. Store it and skip events you have seen. Presence events such as users.typing have no key, since they only matter in the moment. Any recorded delivery can be sent again through the Redeliver Webhook Delivery endpoint, and the replay keeps the original key.

Delivery log

The console shows recent attempts with status codes and errors. The List Webhook Deliveries endpoint returns the same history, filterable by event, date and success. Records are kept for 7 days.

Manage webhooks from code

Besides the console, the API has endpoints to list, create, show, update and delete webhooks. A SaaS can register its own endpoint for each customer team without manual setup. If you prefer typed clients for the rest of the API, see the OnlyFans API SDKs.

No-code triggers

The instant triggers in the Make integration and Zapier integration are webhooks under the hood. The n8n integration reaches the same events. A team without a developer can still react to new subscribers or tips.

Example payload and signature check

Every event arrives as one POST request with a JSON body. The body always has three top-level fields: event, account_id and the event-specific payload. This is the example transactions.new payload from the Fans API docs, unchanged:

{
  "event": "transactions.new",
  "account_id": "acct_123",
  "payload": {
    "id": "abc123",
    "created_at": "2026-01-01 00:00:00",
    "type": "message",
    "tips_source": null,
    "amount": 10,
    "vat_amount": 0,
    "tax_amount": 0,
    "net_amount": 8,
    "fee_amount": 2,
    "currency": "USD",
    "description": "Payment for message from \"<a href=\"https://onlyfans.com/johndoe\">John Doe</a>\"",
    "status": "loading",
    "fan": {
      "id": "123",
      "username": "johndoe",
      "name": "John Doe",
      "display_name": "",
      "avatar": null
    },
    "fanData": {
      "available": true,
      "last_updated_at": "2026-01-01T00:00:00.000000Z",
      "spending": {
        "total": 6.6,
        "messages": 10,
        "subscribes": 2.6,
        "posts": 0,
        "tips": 4,
        "streams": 0
      },
      "previous_reply_at": null
    }
  }
}

The type field tells you what was paid for: a message, post, tip, new or recurring subscription, stream or other. Here the fan paid $10 for a message, and the creator nets $8 after the $2 fee.

To check the signature, hash the raw request body with HMAC SHA256, using your signing secret as the key. This is the JavaScript example from the webhook signature guide:

const crypto = require("crypto");

const computedSignature = crypto
  .createHmac("sha256", signingSecret)
  .update(requestContent)
  .digest("hex");

Compare computedSignature with the Signature header and reject the request if they differ. Hash the body exactly as it arrived, before any JSON parsing, or the values won’t match. The guide has the same check in PHP, Python, Go, Java and Ruby.

Are OnlyFans webhooks safe to use?

Webhooks only send you data about events. They don’t change anything on the creator’s account, so the main risks are on your side: forged requests and data you mishandle. A signing secret deals with the first. Without one, anyone who learns your endpoint URL could post fake events to it. Sender IP addresses change, so the docs say to verify the signature rather than allowlist IPs.

Payloads contain fan names, usernames and spending, so treat your endpoint like any system holding customer data. The connection to OnlyFans itself carries the same platform-terms risk as the rest of Fans API, which the OnlyFans API page explains. For reliability, the delivery and retries guide gives the rules. Answer within 10 seconds, do heavy work afterwards, and expect duplicates.

Pricing

Webhooks have no price of their own. They come with a Fans API plan and use its credits. The Fans API pricing page lists webhooks in Basic and Pro but not in the Free plan. The docs say every event type is available on Basic, Pro and Enterprise.

Plan Price Webhooks Credits each month
Free $0 No 100 welcome credits
Basic $69/month Yes 20,000
Pro $299/month Yes 100,000 + 10,000 per extra account
Enterprise Quote Yes, per the docs Custom

Each delivery is charged once, on its final outcome, at 1 credit per 100 events, so retries cost nothing extra. Manual redeliveries are billed like normal ones. For example, a creator whose account generates 30,000 events in a month would use about 300 credits, a small share of the 20,000 in Basic.

Who it’s for, and who should skip it

OnlyFans webhooks are for developers and agencies building on Fans API who need to react to activity as it happens. Typical uses are posting new tips to a team chat, updating a revenue dashboard, starting a win-back flow when a subscription expires, and alerting someone when an account session expires. They are also the base for a custom reply tool. Subscribe to messages.received and answer through the messaging API, though Fans API sells no ready-made fan chatbot.

Skip them if you only need daily or monthly numbers, because scheduled API calls or exports are simpler. Skip them too if nobody can run an endpoint or a no-code workflow. If you want AI assistants to read account data instead, the MCP connector may suit you better.

Pros and cons

Pros

  • 34 OnlyFans event types, from incoming messages and tips to expired subscriptions and finished data exports
  • Optional HMAC SHA256 signature on every request, so you can reject forged calls
  • A stable idempotency key per event makes duplicate deliveries easy to ignore
  • Failed deliveries retry automatically, and any recorded delivery can be replayed from the console or the API
  • Cheap to run, at 1 credit per 100 events, with retries not billed separately

Cons

  • The pricing page doesn't list webhooks on the Free plan, so plan on Basic or Pro
  • You need a public endpoint that returns a 2xx response within 10 seconds, and sender IP addresses can't be allowlisted
  • Only 3 delivery attempts; events that fire while a failing endpoint is paused are lost and must be backfilled from the API
  • Events can arrive twice or out of order, and the delivery log keeps only 7 days of history
  • Each webhook covers one platform, so OnlyFans, Fansly and Fanvue events need separate webhooks

Frequently Asked Questions

Short answers to the questions agencies ask most.

Does OnlyFans have webhooks?

OnlyFans itself offers no public API and no webhooks for developers. The webhooks described here come from Fans API, an independent service that connects to the OnlyFans accounts you manage. It watches those accounts and sends each event to the URL you register. Fans API isn't affiliated with OnlyFans, so treat these as third-party webhooks.

Which OnlyFans webhook events are available?

The docs list 34 OnlyFans events. They cover account status, new transactions, messages received, sent, deleted or liked, PPV unlocks, tips, new, renewed and expired subscriptions, post likes, fan typing and online status, chat queue updates, data exports, fan summaries and media uploads. Fansly and Fanvue have their own event lists, prefixed with fansly. and fanvue.

How do I verify a webhook signature?

Set a signing secret when you add the webhook. Each request then carries a Signature header, which is the HMAC SHA256 of the raw request body with your secret as the key. Compute the same hash on your server and compare the two. If they don't match, reject the request. The docs give examples in PHP, Python, JavaScript, Go, Java and Ruby.

What happens if my endpoint is down?

A failed delivery is retried up to 3 attempts in total, about 10 seconds and then 100 seconds apart. After 20 failed deliveries in a row the webhook is paused and your team admins get an email. Fans API probes the endpoint after a cooldown that grows from 5 minutes up to 6 hours. Events fired during the pause are not stored, so fetch that window from the API.

Can I use webhooks without writing code?

Yes. The Make and Zapier modules include instant triggers, which are webhooks under the hood, and Fans API also has an n8n node. You choose an event in the workflow tool and build the rest visually. Set the trigger to respond as soon as the event is queued, so slow workflow steps don't push the delivery past the 10-second timeout.

Can I build a chatbot on these webhooks?

You can build your own. Subscribe to messages.received, pass the text to your own logic or AI model, and reply through the Send Message endpoint of the API. Fans API doesn't sell a ready-made fan chatbot, so the reply logic, the tone and the safety checks are yours to write and maintain.

Verdict

Fans API webhooks are the right way to react to OnlyFans activity as it happens, instead of polling the API every few minutes. The event list is broad, the payloads include fan spending data, and signing, deduplication and replays are documented properly. You do need somewhere to receive them, either your own server or a Make, Zapier or n8n workflow, and a paid plan.

Best for: Real-time automations that react to new messages and sales

Fans API logo

Webhooks

Fans API plans: free, $69 or $299/mo

Visit Site