canonical: https://jentic.com/apis/logistimatics.com/logistimatics # Logistimatics GPX Account API Jentic publishes the only available OpenAPI specification for GPX Account API, keeping it validated and agent-ready. The Logistimatics GPX Account API exposes endpoints to manage tracked devices, read GPS positions and event history, send remote commands, configure geofences, and orchestrate shipment workflows. Twenty operations cover the device lifecycle (list, retrieve, update), historical data (positions, events, sensor readings), control plane (commands), and shipment management with associated event posting. ## For AI agents Manage GPS tracking devices, fetch positions and events, send commands, configure geofences, and track shipments through the Logistimatics fleet API. ## Scope Does not handle hardware provisioning, billing, or driver mobile applications - use for tracked-device data, commands, geofences, and shipment events only. ## Capabilities - List and retrieve GPS tracking devices via /devices and `/device/{id}` - Stream historical positions per device through GET `/device/{id}/positions` - Read event history (ignition, motion, alerts) on `/device/{id}/events` - Send remote commands to a device with POST `/device/{id}/command` - Read sensor data such as temperature or battery via `/device/{id}/sensor` - Create, update, and delete geofences with /geofence endpoints - Manage shipments and post shipment events through /shipments and `/shipment/{id}/event` ## Use cases ### Real-time Fleet Tracking Dashboard Drive a live dashboard by listing devices via GET /devices and pulling each device's recent positions through GET `/device/{id}/positions.` Combine with /events to surface ignition, harsh-braking, and geofence breaches inline with the map view. Example prompt: Call GET /devices, then for each device id call GET `/device/{id}/positions`?from= and render the latest point on a map. ### Geofence-based Alerting Define operational zones with POST /geofence and listen for entry/exit events via `/device/{id}/events.` Use the geofence id alongside an event-driven service to trigger SMS or email notifications when assets cross critical boundaries. Example prompt: POST /geofence with name='Depot' and a polygon coordinate list to define the warehouse boundary. ### Shipment Event Posting Track multi-leg shipments by creating a shipment record and posting events such as 'picked-up' or 'delivered' via PUT `/shipment/{id}/event.` The chronologically ordered event list provides an auditable timeline for customer support and dispatch reporting. Example prompt: PUT `/shipment/{id}/event` with type='delivered' and timestamp to mark the shipment complete. ### Remote Device Commands Send firmware-supported commands to a device with POST `/device/{id}/command` - for example, lock, unlock, or request immediate position. The command is queued; poll GET `/device/{id}/commands` to confirm execution. Example prompt: POST `/device/{id}/command` with body command='lock' to queue a remote lock action. ### AI Agent Fleet Operations via Jentic An agent that handles fleet-ops tickets can read device state, post shipment events, or send commands without managing the bearer token. Jentic exposes the Logistimatics endpoints as MCP tools so the agent picks operations by intent. Example prompt: Through Jentic, search 'get device positions', load GET `/device/{id}/positions`, and execute it for the device id provided in the ticket. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/devices` | List tracked devices | | GET | `/device/{id}/positions` | Get position history for a device | | GET | `/device/{id}/events` | Get event history for a device | | POST | `/device/{id}/command` | Send a remote command | | POST | `/geofence` | Create a geofence | | GET | `/shipments` | List shipments | | PUT | `/shipment/{id}/event` | Post a shipment lifecycle event | ## Key resources - **Devices** — List, retrieve, and update tracked devices - **Positions** — Read historical GPS positions per device - **Events** — Read device event history - **Commands** — Queue and inspect remote commands sent to a device - **Sensors** — Read sensor readings such as temperature, battery, and ignition - **Geofences** — Create, list, update, and delete geofence boundaries - **Shipments** — Manage shipments and post lifecycle events - **Users** — List user accounts on the Logistimatics tenant ## Why Jentic - **Setup:** Wiring the GPX Account API by hand means setting up its bearer auth, attaching the token to each call against api.logistimatics.com, and shaping device, geofence, and shipment requests yourself. Through Jentic you install once, import Logistimatics from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Logistimatics puts the device id in the URL path (`/device/{id}/...`), so a rule can pin your agent to one device: it can read that device's positions and events and nothing else. You choose the operations it may call, so sending a command to a device is not included unless you add it. - **Credential handling:** Your Logistimatics bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get device positions' or 'create a geofence', and Jentic returns the matching Logistimatics operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Samsara API** — Connected operations platform with vehicle telematics and dashcam coverage - **Networkfleet API** — Verizon Connect fleet telematics API - **Detrack API** — Driver-facing delivery tracking app with electronic POD - **AfterShip API** — Customer-facing tracking notifications across 1,000+ couriers ## FAQ ### Why is there no official OpenAPI spec for GPX Account API? Logistimatics does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call GPX Account API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Logistimatics GPX API use? The API uses bearer token authentication. Pass the token as `Authorization: Bearer `. Through Jentic the token is stored encrypted in the vault and injected at execution, so the agent never sees the raw value. ### Can I send commands to a tracked device? Yes. Call POST `/device/{id}/command` with the command name in the body. The command is queued on the device and you can confirm execution by polling GET `/device/{id}/commands.` ### How do I create a geofence? POST /geofence with a name and polygon coordinate list. Use GET /geofences to list existing geofences and DELETE `/geofence/{id}` to remove one when it is no longer needed. ### How do I track a shipment through Jentic? Run `pip install jentic`, search Jentic for 'list shipments', load the GET /shipments operation, and execute it. To post events, search 'post shipment event' and execute PUT `/shipment/{id}/event` with the event type. ### What are the rate limits for the Logistimatics GPX API? The spec does not declare numeric rate limits. Implement exponential backoff on HTTP 429 responses and avoid polling /positions more than once per minute per device. ### Can I limit what my agent is allowed to do with the GPX Account API? Yes. Because you run Jentic One yourself, your own rules decide which GPX Account API operations and credentials your agent may use. Since Logistimatics puts the device id in the URL path (`/device/{id}/...`), you can pin the agent to a single device so it only reads that device's positions and events. You also choose the exact operations it may call, so a write action like POST `/device/{id}/command` stays off-limits unless you explicitly allow it.