Start here
Dev Docs →
Concepts, authentication, request/response format, error handling and step-by-step integration guides written for humans.
ReferenceAPI Reference →
The full Destiny REST surface — 464 endpoints with parameters, typed request bodies, code samples and example responses.
Make your first call
Every endpoint lives under /api/v1 and uses a bearer token.
# 1. Log in — the token comes back in the Authorization response header
curl -X POST https://www.acmdestiny.net/api/v1/auth/login \
-H "Content-Type: application/json" \
-d '{"username":"you","password":"••••"}'
# 2. Call an endpoint with the token
curl https://www.acmdestiny.net/api/v1/units/listing \
-H "Authorization: bearer YOUR_TOKEN"New here? Follow Getting Started, then read Authentication for the token-refresh lifecycle.
Explore by collection
HTTP API301
Units, vehicles, clients, drivers, commands, reports, dashboards, monitoring.
Admin API65
Administrative & platform-management operations.
Geo API44
Geocoding, places and spatial zone lookups.
History Query API52
Historical telemetry & event-count queries over time ranges.
SSE2
Server-Sent Events for live telemetry streaming.