Fanvue is the one platform here that ships its own native webhook subscriptions. CreatorAPI wraps them under your key, then layers its own signed delivery system on top so the same event shape covers Fanvue alongside OnlyFans, Fansly and 4based.
Fanvue's official API ships real webhook subscription endpoints: list, create and delete a subscription that Fanvue itself pushes events to. That already makes Fanvue different from OnlyFans and Fansly, neither of which has an official public API or native webhooks. CreatorAPI reaches Fanvue's native webhooks through the same route pattern as everything else, and on top of that runs its own unified webhook layer, signed with HMAC SHA256, with retries and an event catalog, so your handler code does not need a separate integration per platform.
Native Fanvue events for accounts already on the official API, plus a unified layer that also covers OnlyFans, Fansly and 4based.
List, create and delete a webhook subscription directly on /v1/{account}/native/webhooks/subscriptions, the same official Fanvue endpoints, proxied through your key.
Register a URL once with CreatorAPI's own layer and get one event shape across every connected platform, signed with HMAC SHA256.
If your endpoint is down or answers with an error, the unified layer retries with backoff, so brief outages do not lose events.
List every unified event type with GET /v1/webhooks/events. It covers new messages, sales, renewals and subscribers across platforms.
Trigger a test event against your endpoint before anything real happens, so you can ship the handler with confidence.
Inspect past deliveries when something looks off, on either the native or the unified layer.
Use Fanvue's native subscription endpoint directly, or register once with the unified layer to also cover every other connected platform.
# native: create a Fanvue webhook subscription through the official API curl -X POST \ -H "X-API-Key: $CREATOR_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' \ "https://api.creator-api.com/v1/{account}/native/webhooks/subscriptions" # unified: register once, same event shape across every platform curl -X POST "https://api.creator-api.com/v1/{account}/webhooks" \ -H "X-API-Key: $CREATOR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"url": "https://example.com/hooks/creatorapi"}'
Anything that should react to a fan event within seconds instead of on the next poll.
Push new subscribers and purchases straight into your fan database. Pair webhooks with the Fanvue CRM API and free tag writes.
Post every sale or renewal to Slack, Discord or Telegram the moment it lands. Your chatters see revenue as it happens.
Make, Zapier and n8n all accept incoming webhooks today, so signed events can start any scenario. See the no code page for honest setup notes.
A native subscription write costs 2 credits, matching every other native write. Registering a unified webhook costs 1 credit. The free trial ships with 1,000 credits, no card required, and Fanvue is included in every plan at no extra charge. Full pricing details on the pricing page.
Yes. Fanvue is the exception among the platforms CreatorAPI connects: its official API ships its own webhook subscription endpoints, so events can come straight from Fanvue instead of being reconstructed from polling.
So one integration covers every platform you connect. CreatorAPI's signed webhook layer normalises events from Fanvue, OnlyFans, Fansly and 4based into the same envelope, so your handler code does not need a separate branch per platform.
Send a POST request to the native webhooks subscriptions route for your connected Fanvue account. A webhook write costs 2 credits, matching every other native write.
Every delivery is signed with HMAC SHA256. Your server verifies the signature and rejects anything that does not match, so forged events never reach your logic.
CreatorAPI's unified layer retries the delivery with backoff, so a brief outage does not lose the event. You can also inspect past deliveries in the delivery log.
The unified, signed layer does, under one key. OnlyFans and Fansly have no native webhooks of their own, so for those two platforms CreatorAPI's layer is the only webhook system, built on top of native polling.
Start free with 1,000 credits, register a webhook and see your first event in minutes.