When a message is published to a channel, NTM pushes a copy of the message to each subscriber based on the endpoint (URL) specified in the subscription.

Here is the structure of data being pushed:

Sample Data:

{
    "contextAccount": "",
    "contextContract": "",
    "contextDepartment": "",
    "sourceUserId": "",
    "sourceAppId": "",
    "sourceAppTag": "",
    "messageId": "",
    "originMsgId": "",
    "messageTimestamp": "",
    "messageTitle": "",
    "messageText": "",
    "destinationUserId": "",
    "destinationAppId":""
}

Information below refers to the context that the publisher used to publish the message:

• contextAccount
• contextContract
• contextDepartment

Identity of publisher is captured under:

• sourceUserId: The user who originated/published the message using a user interface.
• sourceAppId: The application/backend service that made the request on its user's behalf.
• sourceAppTag: This tag is used to identify a sub-application

Message from the publisher is captured under:

• messageTitle: Subject of the message
• messageText: Body of the message

• originMsgId: A unique identity that NTM issues to a publisher after accepting the request to publish a message.
• messageId: A unique identity that NTM issues to each consumer. Consumers should use this to uniquely identify their copy of a published message.
• messageTimestamp: The time at which NTM received a message from the publisher

Identity of consumer is captured under:

• destinationUserId: The identity of user at the receiving end.
• destinationAppId: The identity of application/service at the receiving end.