A message object represents a message sent or received by a user. The messaging feature can be used to send location, text, or an attachment. Each message includes a read receipt that can be used to tell whether the message has been sent, delivered to user's device, or read by the user.
The API can be used to send message to a user in the fleet on any fleet admin's behalf. To specify the sender use the
X-USER-ID header as discussed in the API Overview section. As stated in the overview, we support the concept of a system or an API user. The following APIs allow the client to send message on behalf of any fleet admin, but limit access to messages of system user. Similarly the APIs can be used to update read receipts on incoming messages that belong to system user.
For an example of how to use our
/messages endpoints in a typical business scenario, refer to TMS Integration Workflow.