TLGPS INTEGRATIONS / 02
A defined path from fleet source to company use.
TLGPS organizes supported tracking information in a company fleet model. Authorized systems can read selected context or receive supported vehicle updates when access is enabled.
01 / INFORMATION PATH
One source relationship. Shared operational context.
A configured tracking source supplies supported information. TLGPS organizes it by company and vehicle before authorized workspaces and systems use it.
SOURCE / 01
Configured tracking source
A defined provider relationship supplies supported fleet records and states.
TLGPS / 02
TLGPS fleet context
Company · vehicles · devices · current state · available history
USE / 03A
TLGPS workspaces
Fleet overview and tracking context inside TLGPS.
USE / 03B
Authorized company systems
Bounded REST reads or supported Gateway vehicle updates.
02 / REST API V1
Read selected fleet context.
Versioned read endpoints expose company and vehicle resources, including available vehicle history. Each request is bounded by company scope, visibility, permissions, feature access and token abilities.
COMPANY SYSTEM
Authorized system
Requests selected fleet context
TLGPS / REST API V1
Authorized fleet context
03 / GATEWAY
Subscribe to supported vehicle updates.
An authorized connection can subscribe to visible vehicles, receive initial state when available, then supported telemetry updates. No delivery or latency guarantee is implied.
COMPANY SYSTEM
Authorized connection
TLGPS GATEWAY
Permitted vehicle set
Within company scope and access permissions
TECHNICAL HANDOFF
Implementation detail belongs in Documentation.
Read the public REST API V1 and Gateway references. Using these interfaces still requires authorized Company access.
Read the documentation →