Create Message
Posts a message to an existing stream.
Post a message to one existing stream.
Post a new message to the given stream. The stream can be a chatroom,,an IM or a multiparty IM.
You may include an attachment on the message.
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 will be returned.
If the message is sent 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.
Stream ID
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 file attachment.
Optional attachment preview.
Message sent.
Id of the message
Id of the parent message, set when the message is a reply to another message or a forwarded message. Since Agent 20.14.
Timestamp of the message in milliseconds since Jan 1 1970
Message content in MessageMLV2
A representation of a message sent by a user of Symphony
Message data in EntityJSON
Message attachments
Indicates if the message have external recipients. Only present on real time messaging.
Details if event failed to parse for any reason. The contents of this field may not be useful, depending on the nature of the error. Only present when error occurs.
User agent string for client that sent the message. Allows callers to identify which client sent the origin message (e.g. API Agent, SFE Client, mobile, etc)
Indicates the format in which the message was originally sent. This could have been either:
- com.symphony.markdown - Markdown OR Message ML V1
- com.symphony.messageml.v2 - Message ML V2
Message that may be sent along with a regular message if configured for the POD, usually the first message sent in a room that day.
Unique session identifier from where the message was created.
"fa691cd3-484a-4109-aeb2-57c05b78c95b"
Id of the message that the current message is replacing (present only if set)
Id of the message that the current message is being replaced with (present only if set)
Timestamp of when the initial message has been created in milliseconds since Jan 1 1970 (present only if set)
Id the the initial message that has been updated (present only if set)
When false the user/s will receive the message update as unread (true by default)
You can specify one or more attachments to the message. The attachment file can be uploaded along with the message using this endpoint.
You can also specify Structured Objects as part of the message, and use Apache FreeMarker templates with these objects. See Use Apache FreeMarker Templates section below.
Interactive Elements can be sent with your messages. See Sending messages with Symphony Elements section below.
For authentication, you must either use the
sessionToken
that was created for delegated application access, or both thesessionToken
andkeyManagerToken
together.When calling this as an OBO-Enabled Endpoints, use the OBO User Authenticate token for
sessionToken
.
🚧 Known Limitations
You can’t send a message that contains only an attachment without any message content.
message
must contain a least one space.DLP (Expression Filters) only works with 1.53 version onwards.
Symphony Elements only works with 1.55.3 version onwards.
To send messages to not public rooms, the caller needs to be part of the stream.
To send numeric cashtags as signals, add a
*
before the number such as$*122450
. E.g.<messageML><cash tag="*122450"/></messageML>
For more information, refer to Message Format - MessageML.Attachments: The limit is set to 30Mb total size; also, it is recommended not to exceed 25 files.
For more information on the size limits of messages, please refer to Messages under the section Messages Size Limits.
Sending messages with Symphony Elements
Symphony Elements is a collection of interactive elements that can be sent within messages to facilitate communication with Symphony users.
Through the use of the elements, bots can send messages that contain forms with text fields, dropdown menus, person selectors, buttons and more! To use the Elements, you just need to call the /agent/v4/stream/:sid/message/create
API using the MessageML format. For more information and examples, refer to Symphony Elements.
Sending Symphony Elements is only supported for SYSTEM
users (Service Accounts).
Use Apache FreeMarker Templates
The message
and data
parameters of the Create Message v4 endpoint supports using Apache FreeMarker templates with Structured Objects.
Important! To support the use of Freemarker variables, the top-level variable name in the div
or span
tag in <messageML>
must be $entity
or $data
.
Using the Freemarker template, you can also create tables that contain a special column with checkboxes
or buttons
on it, allowing users to select one or more rows of the table. For more information, refer to Symphony Elements - Table Select.
The first and second examples show the FreeMarker template content enclosed in <messageML>
for the message
parameter and the associated data model for the data
parameter. The third example shows the resulting PresentationML representation of the message.
See also cURL - Message + Data in the examples below.
Other request examples
📘 See also
Message MessageML Message ID Message Format - MessageML PresentationML Message Format - ExtensionML Colors Symphony Elements
Last updated