Send a mass message
Changed onSend a message to multiple users based on selected lists.
If scheduledAt (or alias scheduled_at) is provided, the message is queued for scheduled delivery instead of being sent immediately.
Request
- Base URLhttps://api.fanvue.com
- URLhttps://api.fanvue.com/chats/mass-messages
- AuthOAuth 2Authorization code: https://auth.fanvue.com/oauth2/authToken URL: https://auth.fanvue.com/oauth2/token scopes: write:chat, read:fan
Headers
API version to use for the request
Opaque key that makes a send safe to retry. A mass send can take longer than the request timeout, and the campaign is already committed by then, so retrying without a key can deliver the broadcast twice. Reuse the same key on a retry: the original result is replayed once the first attempt finished, and a retry while it is still running is rejected with 409 rather than starting a second send. A key reused for a different message is rejected with 409 too, so pick a new one per send. Keys are scoped to your app and the sending creator, and are remembered for 24 hours.
Request body
Response
Mass message sent successfully
Changes
- breaking
the response property
became nullable for the status - info
added the new optional request property
/ - info
added the new optional request property
/ - info
added the optional property
to the response with the status
- breaking
- info
added the new optional
headerrequest parameterIdempotency-Key - info
added the non-success response with the status
- info