GPX Account Api

Name: GPX Account Api API
Brand: GPX Account Api
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementbearer20 EndpointsREST

For Agents

Manage GPS tracking devices, fetch positions and events, send commands, configure geofences, and track shipments through the Logistimatics fleet API.

Connect the GPX Account Api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GPX Account Api, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with GPX Account Api API.

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

GET STARTED

Start building with GPX Account Api API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for GPX Account Api, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use GPX Account Api API for, with concrete tasks.

★ 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.

Call GET /devices, then for each device id call GET /device/{id}/positions?from=<startISO> 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.

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.

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.

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.

Through Jentic, search 'get device positions', load GET /device/{id}/positions, and execute it for the device id provided in the ticket.

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for gpx account api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Logistimatics bearer token is stored encrypted in the Jentic vault and injected at execution time, so agents query device data without ever seeing the raw token.

Intent-based discovery

Agents search by intent (e.g. 'get device positions' or 'create a geofence') and Jentic returns the matching Logistimatics operation with its input schema.

Time to first call

Direct Logistimatics integration: 1-2 days to wire up auth, position polling, and command queueing. Through Jentic: under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Samsara API

Connected operations platform with vehicle telematics and dashcam coverage

Choose Samsara when you need integrated dashcams, ELD compliance, and a richer fleet-ops product surface.

Alternative

Networkfleet API

Verizon Connect fleet telematics API

Pick Networkfleet when the buyer is already a Verizon Connect customer and the vehicles run their hardware.

Complementary

Detrack API

Driver-facing delivery tracking app with electronic POD

Combine Detrack with Logistimatics when you need driver mobile apps and proof-of-delivery alongside raw GPS tracking.

Complementary

AfterShip API

Customer-facing tracking notifications across 1,000+ couriers

Use AfterShip alongside Logistimatics when end-customers need branded shipment tracking pages and notifications.

FAQs

Specific to using GPX Account Api API through Jentic.

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 at https://app.jentic.com/sign-up.

What authentication does the Logistimatics GPX API use?

The API uses bearer token authentication. Pass the token as `Authorization: Bearer <token>`. 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.