Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.catenatelematics.com/llms.txt

Use this file to discover all available pages before exploring further.

​
v2.2.0 - Fleet References & TSP Expansion
14th January 2026
This minor release adds partner system reference tracking across all telematics resources and significantly expands supported telematics service provider (TSP) integrations.
Minor Release: This release includes backward-compatible additions to response schemas and enum expansions. No breaking changes to existing integrations.

​
New Response Fields

A new fleet_ref field has been added to all major telematics resource schemas to support partner system reference tracking.Schemas Updated:
  • hos_availability
  • hos_event
  • hos_violation
  • ifta_summary
  • user
  • vehicle
  • vehicle_location
Field Details:
  • Type: string | null
  • Description: The reference of the fleet in the partner system
  • Required: Yes (nullable)
Example Response:
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "fleet_id": "fleet_123",
  "fleet_ref": "PARTNER_FLEET_ABC",
  "source_name": "samsara",
  "connection_id": "conn_456",
  "source_id": "vehicle_789"
}
Use fleet_ref to maintain bidirectional references between Catena resources and your internal fleet management system identifiers.

​
Backward Compatibility

All changes in this release are backward-compatible:
  • New field fleet_ref: Nullable field added to response schemas. Existing API consumers can safely ignore this field.
  • No endpoint changes: All existing endpoints maintain the same paths, parameters, and behavior.
No migration required for existing integrations.

​
Need Help?

API Reference

View complete endpoint documentation with current API structure

Contact Support

Questions about migrating your integration? Our team is here to help