ACM Destiny API
Welcome to the developer documentation for the ACM Destiny API — the REST interface to the ACM Destiny fleet management and telematics platform.
These docs are split into two surfaces, which you can switch between from the top navigation:
- Dev Docs (you are here) — concepts, authentication, conventions and step-by-step guides written for humans.
- API Reference — the complete, machine-generated reference for every endpoint, with parameters, request bodies, response schemas and live code samples.
Overview
All API communication with Destiny is organised around REST. The API has predictable, resource-oriented URLs, accepts and returns JSON, and uses standard HTTP verbs and response codes.
https://www.acmdestiny.net/api/v1
Every endpoint is served under the /api/v1 prefix on the ACM Destiny API host
(https://www.acmdestiny.net). A full call therefore looks like
https://www.acmdestiny.net/api/v1/users/basic.
The five API collections
The Destiny surface is large — 464 endpoints — and is grouped into five collections:
| Collection | What it covers |
|---|---|
| HTTP API | The core platform: units, vehicles, clients, drivers, unit groups, commands, reports, dashboards, monitoring and more. |
| Admin API | Administrative and platform-management operations. |
| Geo API | Geographic services — geocoding, places and spatial lookups. |
| History Query API | Historical telemetry and event queries over time ranges. |
| SSE | Server-Sent Events guide for real-time streaming. |
Browse them all in the API Reference.
How to read these docs
If you are integrating for the first time, follow this order:
- Getting Started — make your first authenticated call.
- Authentication — obtain and refresh your bearer token.
- Requests & Responses — formats, headers and conventions.
- Errors — how failures are reported.
- Data Model — the difference between Units, Vehicles, Clients and more.
This site is generated from ACM's Destiny Postman collections. The API Reference is produced directly from those collections, so it reflects the real request and response shapes captured against a live Destiny server.