The API Report CardAPI Index
DispatchTrack

DispatchTrack API

Fleet / Trucking / Logistics · dispatchtrack.com

REST APIs and webhooks are published across three documentation properties: the Planner API, the legacy Beetrack API, and a webhook reference. API keys are managed in account settings, with OAuth 2.0 carried over from Beetrack. No official OpenAPI spec or first-party SDK exists.

Last verified: July 2026Logistics & Supply Chain
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceGOODREST APIs and webhooks are published across public doc sites including apidocs-planner.dispatchtrack.com and apidoc.beetrack.com.
AccessGOODCustomers generate API keys in PlannerPro account settings; OAuth 2.0 is also supported, with no partner gate documented.
CoverageGOODResources span orders, routes, drivers, vehicles, customers, proof of delivery, and tracking events.
AuthGOODSelf-managed API keys from account settings plus OAuth 2.0 carried over from the Beetrack platform.
Docs & DXFAILDocs are split across three sites with no official OpenAPI spec, no first-party SDK, and undocumented rate limits.
StabilityMIXEDThe legacy Beetrack API persists alongside the newer Planner API post-acquisition, splitting surfaces and auth models.
Supergood: DispatchTrack has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

DispatchTrack scores F on the API Report Card. REST APIs and webhooks are published across three documentation properties: the Planner API, the legacy Beetrack API, and a webhook reference. API keys are managed in account settings, with OAuth 2.0 carried over from Beetrack. No official OpenAPI spec or first-party SDK exists.

Tried to integrate with DispatchTrack?