Skip to main content
Technical Preview

Overview

Client-mode REST API connector for Geotab MyGeotab JSON-RPC (GetFeed, Device, TextMessage). BASE_ADDRESS defaults to https://my.geotab.com. Auth: Session via Authenticate (JSON-RPC); then credentials.sessionId. Pass secrets only at runtime via MQTT JSON placeholders or Hub GET SECRET — never commit real credentials.

Auth

Session via Authenticate (JSON-RPC); then credentials.sessionId. Prefer Hub secrets / GET SECRET. Never hard-code tokens into the .lot.

Basic Syntax

MQTT topics

Request topics under integrations/geotab/request/...; responses on integrations/geotab/response/....

Template reference

Generated from the shipped broker template geotab (-routeCode GEOTAB). It lists every event the template defines.

Auth

Session via Authenticate (JSON-RPC); then credentials.sessionId

Template parameters

BASE_ADDRESS default: https://my.geotab.com.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call Authenticate by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026