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.
Use this API with AI (Claude, Claude Code, etc.)
Not a developer? Paste the URL below into Claude or Claude Code with your task — the assistant gets the entire API in context and can write the integration for you. The link is tier-aware: you only see endpoints you're allowed to use.
https://api.acmtrack.com/llms-full.txt
Example prompt: “Here's the ACM Destiny API: https://api.acmtrack.com/llms-full.txt. Write me a Python script that pulls my vehicle list every morning at 7 a.m. and emails it to me.”
Also available: a small /llms.txt index for AI navigation, and the machine-readable OpenAPI specs at /openapi/.
Explore by collection
Units, vehicles, clients, drivers, commands, reports, dashboards, monitoring.
Administrative & platform-management operations.
Geocoding, places and spatial zone lookups.
Historical telemetry & event-count queries over time ranges.
Server-Sent Events for live telemetry streaming.