The Messaging API allows you to communicate with the fleet drivers on behalf of a fleet admin. You can
send important updates such as a location, text message, or attachments to the driver’s Motive mobile
app (iOS & Android). The Messaging API also lets you know if the message has been sent, delivered, or
read by the driver/user.

With the Messaging API, you can provide frequent updates to your drivers promptly, thus improving
your overall operational efficiency.

NOTE: To send messages to your drivers, you must specify the “User ID” in the header of the
Messaging API.

Fetch a list of all the updated messages

• Endpoint: v1/messages
• Purpose: Use this endpoint to fetch a list of all the messages that you have sent to your drivers. This allows you to see the body of the message and also whether the driver has seen the message or not.
• Use Case: For Fleet Managers and Operators it is crucial to see all the messages that they've sent to the their drivers and also have a record of them. In Trucking or Logistical business, messages are usually sent to give out instructions to the drivers. The instructions could be regarding a dispatch or drop location. In case, of any miscommunication, the fleet manager or the driver can always refer to the message and either give or receive the correct instructions.

Send a message to a user

• Endpoint: v1/messages
• Purpose: Use this endpoint to send a message to the driver. You must specify the ID of the recipient as well as the body of the message.
• Use Case: In Trucking or Logistical business, messages are usually sent to give out instructions to the drivers. The instructions could be regarding a dispatch, drop location, change of pickup, or any other operational info. Efficient operations require fleet managers to send messages on the fly, and this endpoint helps you do this.

Update the status of messages

• Endpoint: 1/messages
• Purpose: Use this endpoint to update the status of messages. You must specify the ID of the message as well as the status. Allowed values for status is read or delivered.
• Use Case: On a regular day to day operations for your fleet, you must be receiving and sending many messages to the drivers. Marking the messages as either delivered or read, allows you to categorize the messages, and you will know which of the messages that you've sent to your drivers has been delivered or read. If the message is just delivered and not read, then it means that the driver has not yet looked at the message. You can then contact the driver and inform them to look at the message and take action accordingly. This helps for efficient fleet operations.

Fetch a list of all messages for user (using a date range)

• Endpoint: v2/messages/
• Purpose: Use this endpoint to fetch all the messages during a certain time.
• Use Case: As mentioned earlier, daily fleet operations require you to send many messages to your drivers. Instead of fetching all the messages that you've sent, you can also narrow down the search by specifying a date range. The endpoint will fetch only those messages that you've sent during that particular period, making it easy and convenient for you to look at the messages.

Send bulk messages to your users

• Endpoint: v2/messages
• Purpose: Use this endpoint to send the same message to all of your users or drivers.
• Use Case: Fleet operations often requires its managers to be in constant contact with the drivers and also keep them updated about latest developments. Some times they are also required to send company-wide information or regulatory information such as the last date for filing IFTA taxes. For such use cases, you can use this endpoint and keep all of your drivers informed about the important developments.