Use the following steps when a T3 API integration cannot authenticate, returns an error, or provides missing or unexpected data.
Confirm the correct API and credential
T3 API keys are used for T3 fleet-data endpoints. Reporting API tokens are used for Reporting API endpoints.
Credentials are not interchangeable between the T3 API and Reporting API. Confirm that your integration is using the credential and authentication method documented for the API you are calling.
Check the key status
An account owner can review the API key in Integrations under T3 API.
Confirm that:
The correct account was selected when the key was created.
The key has not expired.
The key has not been revoked.
The integration is using the current key.
If the key has expired or been revoked, create a replacement and update the integration.
Review the request
For authentication, permission, or request failures, confirm:
The endpoint and REST method are correct.
The documented authentication method is being used.
The request does not contain an expired or revoked key.
Any required filters and pagination are applied correctly.
Retry behavior follows the published developer documentation.
Do not create additional keys to bypass rate limits.
Investigate missing or unexpected data
Confirm the following before contacting Support:
The account the key was created under
The expected account coverage
The endpoint being called
Any filters or pagination applied
The affected asset IDs
The date and time of the request
The expected result and actual result
Information shown in T3 Fleet may not always appear in the same format through every API endpoint. Refer to the T3 API developer documentation for available fields and endpoint behavior.
Contact Support
If the issue continues, provide:
The T3 account name and company ID
Whether you are using the T3 API or Reporting API
The authentication method, without the credential value
The API key’s display name, creation date, expiration date, and status
The endpoint and REST method
The error message or HTTP status code
The request or correlation ID, if available
The request timestamp and time zone
The expected and actual results
A minimal, redacted request or response example
The affected workflow and accounts
Never send an API key, client ID, client secret, Reporting API token, password, or authorization-header value. Remove credentials and unrelated customer data from screenshots, requests, responses, and logs before sharing them.
If the API returns data from an organization you are not authorized to access, stop making requests and contact Support immediately.