4based has no official webhooks, so CreatorAPI provides them on top of native access. Register a URL once and receive signed events for things like new messages, pay per view unlocks and subscriber changes.
4based webhooks are HTTP callbacks that push account events, such as a new message or a pay per view unlock, to your server the moment they happen. 4based publishes no official public API, so no official webhooks exist either. CreatorAPI builds them as a first party feature on top of your connected account, the same mechanism it already runs for OnlyFans and Fansly, so your code reacts to events instead of polling.
One registration call, then verifiable events at your endpoint until you say stop.
Send a POST request to /v1/{account}/webhooks with your endpoint URL. A webhook write costs 1 credit.
Every delivery is signed. Verify the signature on your server and drop anything that does not match.
If your endpoint is down or answers with an error, CreatorAPI retries the delivery with backoff. Brief outages do not lose events.
List every event type you can subscribe to with GET /v1/webhooks/events. For 4based that covers messages, pay per view unlocks, chats, subscribers and fans.
Trigger a test event against your endpoint before anything real happens. Ship the handler with confidence.
Inspect past deliveries when something looks off. You see what was sent and how your endpoint answered.
Two calls: list the event catalog, then point CreatorAPI at your endpoint.
# see which event types you can subscribe to curl -H "X-API-Key: $CREATOR_API_KEY" \ "https://api.creator-api.com/v1/webhooks/events" # register your endpoint for a connected 4based account 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 message unlocks straight into your fan database. Pair webhooks with the 4Based CRM API and free tag writes.
Post every pay per view unlock or new subscriber 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.
Registering a webhook costs 1 credit and the free trial ships with 1,000 credits, no card required. Plans start at 39 USD per month and unused credits roll over up to 200 percent of the plan allowance, full details on the pricing page.
No. Like OnlyFans and Fansly, 4based has no official public API, so there are no official webhooks either. CreatorAPI provides webhooks as a first party feature on top of native access through your own connected account.
Send a POST request to the CreatorAPI webhooks endpoint for your connected 4based account with the URL you want events delivered to. A webhook write costs 1 credit.
Every delivery is signed with HMAC SHA256. Your server verifies the signature and rejects any request that does not match, so forged events never reach your logic.
CreatorAPI 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 event catalog is available at the webhooks events endpoint. For 4based it covers new messages, pay per view unlocks, new chats, subscriber changes and new fans. Query it once and pick the events your app needs.
Yes. You can trigger a test delivery against your endpoint and inspect the result in the delivery log before any real event arrives.
Yes. One key covers OnlyFans, Fansly and 4based, and the webhook endpoints follow the same pattern across all three.
Start free with 1,000 credits, register a webhook and see your first signed delivery in minutes.