This article gives an overview of the Symphony message workflow and shows how message representations are used throughout the workflow. In its subpages are presented the specifications of messageML.
When calling API methods that create messages, the content of the message must be sent using MessageML markup. MessageML is a tag-based language that is a subset of XHTML, with the addition of tags specific to Symphony for embedding information (e.g. a mention) into a message.
You can find the specifications of the MessageML language in the attached subpages. Even if they are grouped in different categories for documentation clarity purposes, please note you can do your own mix, respecting the specific rules explained at each component specification level.
Also, please note that messages in MessageML markup are enclosed in a
MessageML has full unicode support and messages should be sent using UTF-8 character encoding.
When creating or retrieving messages using the API, MessageML shorthand tags are translated into equivalent XHTML tags and returned in PresentationML.
Note: MessageML is just a subset of PresentationML that makes it easier to construct messages from your bot. The API can ingest either MessageML or PresentationML. However, the API will only deliver messages as PresentationML to a bot.
MessageML is formatted as XML and should have all tags properly formatted. For example, rather than using
<br>you must use
<br/>. For string attributes, standard rules for escaping XML special characters apply, i.e. escaping:
'(if single quotes are used to quote the value)
"(if single quotes are used to quote the value)
&Other XML named entity sequences such as
>may be used.
Keywords may only contain alphanumeric characters, underscore, dot and dash.
Important: when sending numeric $cashtags as signals, add an
*after the $ sign, for example, $_122450. <cash tag="$_122450"/>