Authentication & tokens
Every request to /api/v1/ is authenticated with a single long-lived API token issued to a MyTrafficData user account. There are no OAuth flows, no refresh tokens, no session cookies — just one header on every request.
API namespace
All endpoints documented on this site live under a single namespace:
API versioning & lifecycle
This page describes how the MyTrafficData external API is versioned.
Breaking-change policy
We do not ship breaking changes inside a major version. Every breaking change goes into a new major (/api/v2/, /api/v3/, …) and the previous major continues to work in parallel.
Deprecation timelines
How we mark an endpoint or version as on its way out — and what you should do when you see the signal.
Rate limits
The MyTrafficData API throttles abusive request patterns to keep the platform fast for everyone. Most well-behaved integrations never hit a limit; this page explains what happens if you do.
Pagination
Endpoints that return collections use cursor-based pagination. You ask for a page of results; if more exist, the response carries an opaque cursor you pass back to fetch the next page.
Timezone handling
All timestamps in the MyTrafficData API are ISO 8601 strings. The only thing that varies between fields is whether the string carries a UTC offset — and that small detail tells you exactly how to interpret the value.
Error model
Error responses from /api/v1/ are always JSON, always carry the matching HTTP status code, and fall into one of three shapes depending on where the error came from.
Best practices
Non-binding recommendations that will make your integration faster, cheaper, and easier to operate. None of these are required — the API works without them — but every one of them has come up in real customer support tickets.