Route One ELD Provider Support
This release expands the Catena platform’s provider coverage by adding Route One ELD (route_one_eld) as a fully supported telematics service provider. The new provider value is available across all data schemas and webhook event types.
Minor release: This is a backward-compatible addition. No changes are required to existing integrations.
New provider support
Route One ELD added to TspEnum and all source_name fields
Route One ELD added to TspEnum and all source_name fields
The value Example — identifying Route One ELD data in a webhook event:
route_one_eld has been added to the TspEnum enumeration and to the source_name field across every data schema in the API. This means you can now filter, identify, and process data originating from Route One ELD devices using the standard source_name field.Affected schemas:Example — filtering data by provider:
No action required
This is a purely additive change. Existing integrations continue to work without modification. If you want to start ingesting data from Route One ELD connections, no code changes are needed — data will appear automatically withsource_name: "route_one_eld" once a Route One ELD connection is established.
Need help?
API Reference
View complete endpoint documentation with current API structure
Contact Support
Questions about your integration? Our team is here to help