Notification order

Please note that in asynchronous systems, the order of notifications or responses cannot be guaranteed due to the nature of concurrent processing. As such, users should be aware that notifications may not always be received in the sequence they were sent.

Concurrent Conversations

A consumer may engage in only one active conversation at a time per brand; any attempt to initiate another conversation will be declined.

Request Submission Restriction

Concurrent requests will be rejected until a response to the current request is received; please avoid submitting additional requests in the meantime. More details under API reference ‘InitConnection’ section

Messages validation

There is ESAPI validation on messages published. Following are the HTML tags that are allowed to be published. Any other tags or tags looking text will be rejected e.g. <>

<b> <i> <p> <br> <a> <ol> <ul> <li> <dl> <dt> <dd> <em> <strong> <tt> <blockquote> <div> <ecode> <quote>