Fanvue's official API ships a real mass message endpoint, not a workaround. Target a custom list or a smart list, send a saved template, and manage the whole campaign lifecycle from your own backend, all under one CreatorAPI key.
On OnlyFans and Fansly, CreatorAPI builds a mass send by looping the single message endpoint from your own backend, because neither platform has a native bulk send. Fanvue is the exception: its official API has a dedicated mass message endpoint plus first party audience tools, so CreatorAPI calls the real thing instead of simulating it.
A single call to Fanvue's mass message endpoint delivers to an audience, list or check what has gone out, list what has sent and delete a message that has not landed yet.
Create a custom list, add and remove members, then send a campaign straight to that list.
Read Fanvue's own smart lists and their members, built in audience segments you did not have to define by hand.
List, create and reuse template messages, so a campaign is one call away instead of retyped every time.
Send in batches and check batch status, so a large campaign does not block on a single request.
List mass messages already sent and their unread counts, so a campaign is measurable, not a fire and forget action.
# create a custom list, then send a mass message to it curl -X POST \ -H "X-API-Key: $CREATOR_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' \ "https://api.creator-api.com/v1/{account}/native/chats/custom-lists" curl -X POST \ -H "X-API-Key: $CREATOR_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' \ "https://api.creator-api.com/v1/{account}/native/chats/mass-messages"
Mass messaging is powerful and easy to overuse, native endpoint or not. CreatorAPI gives you the access; you stay responsible for pace, consent and Fanvue's own rules. Sensible throttling and honest content protect both the creator and the account, and keep campaigns landing where they should.
Yes. Unlike OnlyFans and Fansly, Fanvue's official API ships a native mass message endpoint. CreatorAPI calls it directly instead of looping single sends from your own code.
Yes. Fanvue's own custom lists and smart lists let you group fans and send a campaign to a list in one call, and CreatorAPI exposes both natively.
Yes. Fanvue's template messages let you save a message once and send it again without retyping it, and template management is part of the native API surface.
No. OnlyFans and Fansly have no native bulk send, so CreatorAPI builds a campaign there by looping the single send endpoint against a tagged segment. See the OnlyFans mass messaging page for that pattern.
Get your key, connect a Fanvue account and send to a list in minutes.