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.
Update an existing message.
post
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.
Regarding authentication, you must either use the sessionToken which was created for delegated app access or both the sessionToken and keyManagerToken together.
Starting with SBE v24.1, attachments are supported.
Path parameters
sidstringRequired
Stream ID
midstringRequired
ID of the message to be updated
Header parameters
sessionTokenstringRequired
Authorization token used to make delegated calls.
keyManagerTokenstringOptional
Key Manager authentication token.
Body
messagestringOptional
The message payload in MessageML.
datastringOptional
Optional message data in EntityJSON.
versionstringOptional
Optional message version in the format "major.minor". If empty, defaults to the latest supported version.
attachmentstring · binaryOptional
Optional file attachment.
previewstring · binaryOptional
Optional attachment preview.
silentstringOptional
Optional boolean field that will determine if the user/s should receive the message as read or not (true by default)
Responses
200
Message sent.
application/json
400
Client error, see response body for further details.
application/json
401
Unauthorized: Session tokens invalid.
application/json
403
Forbidden: Caller lacks necessary entitlement.
application/json
451
Compliance Issues found in message or file
application/json
500
Server error, see response body for further details.
application/json
post
/v4/stream/{sid}/message/{mid}/update
For authentication, you must either use the sessionToken that was created for delegated application access, or both the sessionToken and keyManagerToken together.
📘 Controlled Availability
Message 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 the SEND_MESSAGES permission.