Trimac Provider Support
This release adds Trimac as a supported telematics service provider (TSP) across the entire Catena API. All data types that carry asource_name field now recognize trimac as a valid value.
Backward-compatible addition: Existing integrations are unaffected. The
trimac value is additive — no existing enum values were removed or renamed.New provider support
Trimac added to TspEnum and all source_name fields
Trimac added to TspEnum and all source_name fields
The
trimac value has been added to the TspEnum schema and to the source_name enum on every data model in the API. This means you can now:- Filter requests by
source_name=trimacto retrieve data originating from Trimac-connected fleets - Expect
"source_name": "trimac"in webhook event payloads for Trimac fleets - Use Trimac connections through the standard Catena Connect flow
All corresponding webhook event schemas (e.g.
VehicleAdded, HosEventModified, EngineLogAdded, etc.) are also updated.Using the new provider
Once a Trimac fleet is connected via Catena Connect, data flows through the standard API withsource_name set to trimac. No changes to your existing API calls are required.
Need help?
API Reference
View complete endpoint documentation with current API structure.
Contact Support
Questions about integrating with Trimac or other providers? Our team is here to help.