Authentication

The TrackSafe365 API uses access-token authentication for all programmatic access — pass your token directly in the Authorization header (there is no Bearer prefix).

Obtaining an API token

Sign in to your TrackSafe365 organization account
Navigate to Settings → API Tokens
Click Generate new token — give it a descriptive name and select the required scopes
Copy the token immediately — it will not be shown again

Tokens are generated inside the TrackSafe365 safety platform and are prefixed gls_ak_.

Making authenticated requests

Pass your token directly in the Authorization header on every request — do not prepend Bearer:

GET /services/glssafety/api/public/trucks HTTP/1.1
Host: dev-gw.tracksafe365.com
Authorization: gls_ak_xxxxxxxxxxxxxxxxxxxx
Content-Type: application/json

Token scopes

Scope	Description
`trucks:read`	Read truck records
`trucks:write`	Create, update, and delete trucks
`video:read`	Read video requests and dash-cam clips
`events:read`	Read safety detection events
`events:write`	Acknowledge or dismiss safety events
`maintenance:read`	Read DTC alerts and work orders
`webhooks:manage`	Create and manage webhook subscriptions

Security guidelines

Store tokens in environment variables — never commit them to source control
Use the minimum set of scopes your integration requires
Rotate tokens periodically via the dashboard
Revoke compromised tokens immediately under Settings → API Tokens → Revoke