Fansly's own apiv3 ships a real broadcast endpoint, and CreatorAPI exposes it directly instead of faking bulk sends with a loop. Send to your whole audience or a segment, schedule the send, and read stats back once it lands.
Most platforms give you nothing but a single message endpoint, so a mass messaging tool has to loop it call by call. Fansly is different: its own apiv3 has a dedicated message/broadcast route, plus a scheduled variant and a stats endpoint to read results back. CreatorAPI proxies all three natively, so you send one API call and Fansly itself fans the message out to your audience.
One call to message/broadcast sends to your audience through Fansly's own delivery, not a loop over individual chats.
Fansly natively supports scheduling a broadcast for later, so a campaign can go out at the moment that converts best without your server staying online to trigger it.
Combine CreatorAPI tags, subscription state and spend to build a segment, then send to that list instead of the whole broadcast audience.
Read delivery and engagement stats for a broadcast back from Fansly's own stats endpoint once it lands.
A signed event fires on new tips and subscriptions, so you can measure a campaign in real time alongside the native stats.
Each account sends on its own managed residential IP, isolated and revocable.
# send to your Fansly broadcast audience, 2 credits
curl -X POST \
-H "X-API-Key: $CREATOR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"content": "New set just dropped"}' \
"https://api.creator-api.com/v1/{account}/native/message/broadcast"
Mass messaging is powerful and easy to overuse. CreatorAPI gives you the access; you stay responsible for pace, consent and Fansly's own rules. Sensible throttling and honest content protect both the creator and the account, and keep campaigns landing where they should.
Yes. Fansly's own apiv3 exposes a broadcast endpoint plus scheduled broadcasts and broadcast stats, and CreatorAPI proxies it directly instead of looping single sends.
Yes. Combine tags, subscription state and spend to build a segment, so a campaign reaches the right fans rather than the whole broadcast list.
Overusing mass messages carries risk on any platform. One IP per account and your own throttling keep the footprint sensible, and you set consent and content rules.
Yes, though the mechanics differ. OnlyFans has no native bulk send endpoint, so CreatorAPI loops the single send call for OnlyFans campaigns, while Fansly's own broadcast endpoint sends in one call. See the OnlyFans mass messaging API for that version.
Get your key, connect an account and send your first broadcast in minutes.