Developer documentation
Access & scope
Company capabilities, permissions and vehicle visibility.
Authentication, Company availability, permissions, token abilities and resource visibility answer different questions. They are evaluated together.
Company capabilities
Your Company must have the relevant REST API or Gateway capability enabled. An active account or a token does not enable a service by itself. Coordinate capability changes with an authorized TLGPS contact.
User authorization
Effective permissions depend on the person's assigned responsibility/access within the Company's available capabilities. A token cannot expand those permissions. A successful sign-in does not authorize every operation.
Token abilities
An ability restricts what the particular credential may do. For example, vehicles.view-any permits the credential to attempt a vehicle-list read; the owner must still have the matching effective permission and resource scope.
Company and vehicle visibility
Results are bounded by the token owner's effective visibility. A Company can access its own fleet and additional Company scope explicitly made available to it. Additional data visibility does not enable an integration capability or turn the external Company into a selectable Portal workspace.
Unavailable vehicles are not exposed by direct REST lookup. Gateway subscription batches reject unavailable vehicles without distinguishing missing resources from unauthorized resources.
Changes during a connection
REST evaluates access on requests. Gateway rechecks authorization periodically; subscriptions can be removed or a connection closed when access changes. Do not assume immediate revocation or an uninterrupted stream. After reconnecting, authenticate again and recreate only subscriptions still permitted.