Compose messages

Create, edit & manage commands to operate your GPS trackers flexibly using RACEMAP’s message dashboard. This platform empowers you to control and tailor messages to your specific needs.

Access the message dashboard: https://racemap.com/admin/message-templates

Overview over the message dashbord with custom commands and public commands.

The message dashboard provides:

• Private messages: Custom messages you create, accessible only in your account.

• Public messages: Provided by RACEMAP and available for all users.

Key features:

• Device support: Manage message templates for a variety of tracker types supported in RACEMAP. For more details on supported hardware, visit supported GPS devices.
• Ownership control: Private messages can be applied only to devices you own or can edit. These messages cannot be shared with borrowers.

• Template ID: Each template is assigned a unique templateId, which is required when sending messages from external systems.

• Export your private messages as GeoJSON files for external use.

Message operations

Independent from sending commands with the tracker management you can use the public and private templates to integrate message sending into your system.

URL https://racemap.com/api/v1/trackers/messages Method Send

Get the necessary deviceId from the current API.

*/current, location data

Compose your own message templates

• Use the "Add template" button to create a new private message.

• Duplicate & edit: Copy an existing message and modify it to create a private version.

For each message template the below information must be provided.

• Name: The name of the template

• Variant: Either single or group

  • Single: The same template is applicable for one or multiple trackers.

  • Group: Groups several single templates with the same function for different tracker types (e.g., the "Shut down" command for GL300, LK106, and M20 grouped together).

• Description: Explain the effect of the message on the GPS tracker and clarify any parameters, including their units.

• Tracker types: Select the supported trackers to which the message applies.

• Allowed user roles: Specify whether the message can be used by you as the owner and or editors.

• Template: Provide the command, that will be send with the message.

• Arguments: If the command uses parameters, define them here.

• Example: A copyable example of the template.