Update Message
Update an existing message.
Last updated
Was this helpful?
Update an existing message.
Last updated
Was this helpful?
Available on Agent 20.13.1+ with SBE 20.13.2+ in Beta. Starting with SBE 20.16, the feature is now in Controlled Availability. Starting with Agent 23.6, this endpoint is OBO-enabled.
For authentication, you must either use the sessionToken
that was created for delegated application access, or both the sessionToken
and keyManagerToken
together.
📘 Controlled AvailabilityMessage Update is currently released with Controlled Availability because of the following limitations:
This feature is not yet supported on Mobile, where updates are displayed as new messages instead of replacing the existing one.
The flag
silent=false
, that can be used to make an update be displayed as an unread message, is not fully supported yet.Both limits will be lifted in a future release.
🚧 Permissions and guidelines
Entitlement
canUpdateMessage
is required.Wall posts cannot be updated.
It is not possible to update messages sent by other users (except when using OBO with the proper permissions)
There is no time limit to update old messages, however we discourage updating very old messages as this won't provide a good user experience.
There is no limit of how many times a message can be updated, but we discourage updating it more than a 1000 times.
When used as a OBO endpoint, the end user must have the
canUpdateMessage
entitlement enabled, and the App must have theSEND_MESSAGES
permission.
Update an existing message. The existing message must be a valid social message, that has not been deleted.
The message can be provided as MessageMLV2 or PresentationML. Both formats support Freemarker templates.
The optional parameter "data" can be used to provide a JSON payload containing entity data. If the message contains explicit references to entity data (in "data-entity-id" element attributes), this parameter is required.
If the message is in MessageML and fails schema validation a client error results
If the message is updated then 200 is returned.
Regarding authentication, you must either use the sessionToken which was created for delegated app access or both the sessionToken and keyManagerToken together.
/v4/stream/{sid}/message/{mid}/update
Stream ID
Parent message ID
Authorization token used to make delegated calls.
Key Manager authentication token.
The message payload in MessageML.
Optional message data in EntityJSON.
Optional message version in the format "major.minor". If empty, defaults to the latest supported version.
Optional boolean field that will determine if the user/s should receive the message as read or not (true by default)