From zero to integrated in three steps
The fastest way to a working integration is to follow the path below.
Get a token
Generate an API token from your MyTrafficData account. The plaintext is shown once — copy it into your secret store.
Read more →02Send your first request
Pass the token in the Authorization header. List your sites, fetch records, or create an export — all REST, all JSON.
Read more →03Build with the rules
Read the concepts pages once: pagination, rate limits, timezones, errors. Then ship integrations that don’t break on edge cases.
Read more →What you can build
The external API exposes four resource families. Each is documented end-to-end.
Traffic data
Search vehicle and meta records across every site you own. Cursor-paginated, time-windowed, filterable by direction, status, speed, and length.
Explore →Exports
Create async export jobs for historical data, poll the job until ready, download the file. No 30-day limit on exports.
Explore →DSD Flex triggers
Activate or deactivate display triggers remotely. Idempotency-key supported so retries are safe across the network boundary.
Explore →Batch operations
Track multi-device commands as a single batch. Get a summary, per-device results, and ETag-based polling that returns 304 when nothing changed.
Explore →- 13Endpoints
- JSONWire format
- TokenAuth model
- RFC 7807Errors (v2)
- ISO 8601Timestamps
Ready to build?
The quickstart takes about five minutes. The concepts section answers the questions you’ll have on day two.