Get Messages

Get messages from an existing stream.

A caller can fetch all unseen messages by passing the timestamp of the last message seen as the since parameter and the number of messages with the same timestamp value already seen as the skip parameter. This means that every message will be seen exactly once even in the case that an additional message is processed with the same timestamp as the last message returned by the previous call, and the case where there are more than maxMessages with the same timestamp value.

This method is intended for historic queries and is generally reliable but if guaranteed delivery of every message in real time is required then the equivilent firehose method should be called.

Stream ID
Timestamp of first required message. This is a long integer value representing milliseconds since Jan 1 1970
No. of messages to skip.
Max No. of messages to return. If no value is provided, 50 is the default. The maximum supported value is 500.
Session authentication token.
Key Manager authentication token.
200: OK
204: No Content
No Messages.
400: Bad Request
Client error, see response body for further details.
401: Unauthorized
Unauthorized: Session tokens invalid.
403: Forbidden
Forbidden: Caller lacks necessary entitlement.
500: Internal Server Error
Server error, see response body for further details.

📘 Optional attributes returned

Note that some attributes are returned in the payload only under specific conditions:
  • sharedMessage only when the message represented by this class is a wall post sharing another message;
  • initialMessageId, initialTimestamp, and replacing only when the corresponding message is sent as an update to another message thanks to Update Message endpoint. Note that the first two attributes relate to the original (and therefore first) message sent, whereas the replacing attribute relates to the message that has been updated by this message;
  • replacedBy only when this message has been updated by a new message. It contains the id of the replacing message.
  • parentMessageId only when this message is a reply or a forward of another message which id is returned in this attribute.

Pagination usage

• The skip parameter is supposed to be used to skip messages that have the same timestamp as the one specified on since.
• Pagination is supposed to use the since parameter instead of skip and limit.
If you want to get two messages at a time skipping the ones you have already seen, the calls should be the following:
  1. 1.
    First call
  2. 2.
    Second call Let's assume here that the timestamp from the message returned on the first call was 1551052800000 and there was no other message with that same timestamp returned.
It returns the two messages received after or on the timestamp 1551052800000, skipping one message from that same timestamp (which is the one you have already seen).
Note that you can keep doing this process with subsequent calls.

📘 Supported stream types

In addition to conversation streams such as IM, MIM, Chat rooms and Wall posts, Symphony also supports other types of streams, some of them reserved for internal use. These other stream types (ACTION, POST, PRIVATE_CHANNEL, MEETING, SUPPRESS_JUSTIFICATION) are not supported by the Get Messages endpoint.
Last modified 2mo ago