Developers
One API for every tracker you sell.
Nexara terminates the device protocols, decodes them, and hands you a single normalized event model over REST and webhooks. Write your application once; change hardware without touching it.
What happens to a packet
Everything between the antenna and your application is Nexara's problem, not yours.
- 1GPS deviceQueclink, Teltonika, Concox, Meitrack, AsiaTelco
- 2IngestionTCP / UDP listeners per protocol
- 3Protocol decoderPer-manufacturer parsing
- 4Normalized eventOne shape, every vendor
- 5REST API / webhookRead it or have it pushed
- 6Your applicationYour product, your brand
The surface
Live routes on the platform today, under the /api/v1 prefix. Authenticate with a JWT session or a programmatic API key.
Positions
Current and historical location for any device, and proximity search.
GET /api/v1/positions/latest GET /api/v1/positions/nearby GET /api/v1/devices/:id/positions
Devices
Inventory, lookup and per-device stream configuration.
GET /api/v1/devices GET /api/v1/devices/:id GET /api/v1/devices/search PATCH /api/v1/devices/:id/stream
Trips
Journeys derived from raw telemetry — start, end, distance, duration.
GET /api/v1/trips GET /api/v1/trips/:id
Geofences
Polygon and radius boundaries, containment tests and occupancy.
GET /api/v1/geofences GET /api/v1/geofences/containing GET /api/v1/geofences/:id/devices-inside GET /api/v1/geofences/:id/check
Alerts
Rule definitions and the catalog of conditions you can build on.
GET /api/v1/alerts/catalog GET /api/v1/alerts/rules POST /api/v1/alerts/rules PUT /api/v1/alerts/rules/:id
Commands
Send instructions back down to hardware, and cancel them in flight.
POST /api/v1/commands/device/:deviceId GET /api/v1/commands/:id POST /api/v1/commands/:id/cancel
Webhooks
Outbound delivery with HMAC signing and rotatable secrets.
GET /api/v1/webhooks PUT /api/v1/webhooks/:id POST /api/v1/webhooks/:id/regenerate-secret DELETE /api/v1/webhooks/:id
Hardware changes. Your code doesn't.
Connect different GPS hardware without rewriting your application for every manufacturer. The decoder absorbs the difference; your code sees one event shape.
See the full device compatibility list, or read how existing hardware moves onto the platform.
Build on the telemetry, not the protocols.
Take the API on its own, or layer the distributor tooling and white-label tracker on top of it later.