Stopping Messages
Stopping messages by uuid
POST
https://direct.revicom.ltd/api/v1/message/stop
The method allows for permanent cancelation of single messages with identifiers transmitted
Headers
Authorization*
string
Basic {TOKEN_1}
Content-Type*
string
application/json
Request Body
uuids*
array
Array of message identifiers; at most 10,000 values are allowed.
If the request is correct, a response will list the message stopping statuses.
Changing the status of messages is asynchronous: it can take a few seconds between successful completion of the request and the status of messages being set to unsent.
This request can be performed for both single messages and dispatch messages
When a root cascade message is successfully stopped, the entire cascade from that message will be stopped
Response object description
errors
boolean
Unsuccessful message stops (codes 403, 404 in the response)
items
array
Array with message stop result objects
items.messageUuid
string
Message ID
items.code
integer
Message stop result:
200 — the message will be stopped for sure
202 — the message will be stopped not for sure, because it enters the stage of sending or generating a cascade message
403 — the message cannot be stopped because it is being sentor already sent
404 — the message was not stopped because it was not found
Request example
Last updated