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.
This minor release adds fleet-based filtering capabilities to the connections endpoint and extends the Connection schema with partner system reference tracking.
Minor Release: This release includes backward-compatible additions to query parameters and response schemas. No breaking changes to existing integrations.
New Query Parameters
Fleet Filtering for Connections
Fleet Filtering for Connections
The
GET /connections endpoint now supports filtering by fleet identifiers using two new optional query parameters.New Parameters:fleet_ids- Filter by Catena’s internal fleet IDs (array of UUIDs, max 100 items)fleet_refs- Filter by your organization’s fleet reference identifiers (array of strings, max 100 items)
- Retrieve connections for specific fleets in your organization
- Use
fleet_idswhen working with Catena’s fleet identifiers - Use
fleet_refswhen working with your own fleet reference system
New Response Fields
Connection Fleet Reference
Connection Fleet Reference
A new
fleet_ref field has been added to the Connection schema to support partner system reference tracking.Field Details:- Type:
string | null - Description: The reference of the fleet in the partner’s system
- Required: Yes (nullable)
Backward Compatibility
No Breaking Changes
No Breaking Changes
All changes in this release are backward-compatible:
- New query parameters: Optional parameters added to
/connectionsendpoint. Existing API calls without these parameters continue to work unchanged. - New field
fleet_ref: Nullable field added to Connection response schema. Existing API consumers can safely ignore this field. - No endpoint changes: All existing endpoints maintain the same paths and behavior.
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