TraffiTech Docs
Documentation for TraffiTech's platform and integrations.
The platform APIs are how you read and write fleet data programmatically - two APIs sharing one access token.
Adapters provide per-organization integrations with your own systems and third-party services.
TraffiTech Auth is our identity platform - a self-hosted OpenID Connect provider that handles sign-in, federation with enterprise directories, and user provisioning.
Where to start
- API reference - both platform APIs, generated from the running services:
- Core API (REST) - the write path for organizations, users, vehicles, devices and drivers
- Vehicle Data API (GraphQL) - the read path for telemetry, journeys, behaviour events and reporting
- Identity & access - signing users in and keeping accounts in sync:
- Single Sign-On (SSO) - federate sign-in with Microsoft Entra ID (Azure AD)
- User Provisioning (SCIM) - push user accounts from your directory into TraffiTech on a schedule
- Protocol reference - deep dives on OpenID Connect and OAuth 2.0
- Adapters - per-organization integrations with your systems (e.g. Tacho FTP Sync to deliver tachograph files to your own (S)FTP server)
- Frontend Apps - user manuals for TraffiTech's web applications
Which API do I need?
Both APIs authenticate with the same OAuth 2.0 access token from the identity service, so the choice is about what you are doing rather than how you connect.
| You want to | Use |
|---|---|
| Create or change an organization, user, vehicle, device, camera or driver | Core API |
| Check what a user is permitted to do | Core API |
| Read positions, journeys, trips, behaviour events or timeseries | Vehicle Data API |
| Build a report, dashboard or export | Vehicle Data API |
New read-heavy functionality lands in the Vehicle Data API. The Core API is in maintenance but remains the only place to write the entities above.