ZAITRACK for developers
ZAITRACK's public API v1 is one HTTPS API for your organisation's fleet: vehicles, drivers, devices, positions and tracks, trips, geofences, alerts and their rules, dispatch jobs, device commands, fuel, maintenance, reports and webhooks. Every operation is listed in the API reference, generated from the gateway's route table.
What you need
- An organisation on ZAITRACK and a member account in it. You sign in to the console and to Developer Studio with the same account.
- A sandbox and a test key, made in Developer Studio: see Get access.
- An HTTP client. No SDK is published yet: see SDKs. Every example here is
curl.
How the API behaves
- JSON request and response bodies with camelCase keys. Ids are UUIDs. Times are RFC 3339 in UTC.
- Lists return
{"items": [...], "nextCursor": "..."}: see Pagination. - Errors are RFC 9457
application/problem+jsonwith a ZAITRACK code: see Errors. - Writes that change a resource you read take its version in
If-Match: see Conventions. - Creates and actions accept an
Idempotency-Key; device commands require one: see Idempotency. - Every operation has a rate class with limits per organisation: see Rate limits.
- Events reach you as signed webhooks: see Webhooks.
Where things are
| Host | What it is |
|---|---|
api.zaitrack.app | The public API (see Regions for the region hosts) |
auth.zaitrack.app | The OAuth 2.1 and OpenID Connect issuer |
| developer-studio.zaitrack.app | Developer Studio: API keys, OAuth apps, webhooks, sandboxes, usage |
| adapter-studio.zaitrack.app | Adapter Studio: publish adapters |
| marketplace.zaitrack.app | The marketplace: codecs, connectors and data sources |
| zaitrack.app | The console |