Skip to main content
PATCH
/
chats
/
mass-messages
/
{messageUuid}
Update a scheduled mass message
curl --request PATCH \
  --url https://api.example.com/chats/mass-messages/{messageUuid} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Fanvue-API-Version: <x-fanvue-api-version>' \
  --data '
{
  "text": "<string>",
  "mediaUuids": [
    "3c90c3cc-0d44-4b50-8888-8dd25736052a"
  ],
  "price": 301,
  "includedLists": {
    "smartListUuids": [],
    "customListUuids": [
      "3c90c3cc-0d44-4b50-8888-8dd25736052a"
    ]
  },
  "excludedLists": {
    "smartListUuids": [],
    "customListUuids": [
      "3c90c3cc-0d44-4b50-8888-8dd25736052a"
    ]
  },
  "scheduledAt": "2023-11-07T05:31:56Z"
}
'
{
  "error": "<string>",
  "message": "<string>"
}
Required scope
  • write:chat — Create new chats and send messages. This scope is required for any chat-related actions that modify data.

Authorizations

​
Authorization
string
header
required

OAuth 2.0 access token, presented as a JWT bearer token in the Authorization header. Obtain a token via the authorization-code flow; the scopes granted to the token determine which operations it may call.

Headers

​
X-Fanvue-API-Version
string
default:2025-06-26
required

API version to use for the request

Example:

"2025-06-26"

Path Parameters

​
messageUuid
string<uuid>
required

Body

application/json
​
text
string
Maximum string length: 5000
​
mediaUuids
string<uuid>[]
​
price
number | null
Required range: x >= 300
​
includedLists
object
​
excludedLists
object
​
scheduledAt
string<date-time>

Optional scheduled date/time in ISO 8601 format. Alias scheduled_at is also accepted.

Response

Mass message updated successfully