RigBot Provider Support
This release adds RigBot as a supported telematics service provider (TSP) across the Catena API. All data schemas that include asource_name field now recognize rigbot as a valid value.
New integration: RigBot is now available as a data source across all telematics, HOS, DVIR, fleet, and webhook event schemas.
New provider support
RigBot added to source_name enum
RigBot added to source_name enum
The Filtering by RigBot source:
rigbot value has been added to the source_name field across all resource schemas and webhook event payloads. This includes:- Vehicles, trailers, and locations
- Drivers and driver-vehicle associations
- HOS events, daily snapshots, availability, and violations
- DVIR logs
- Engine logs and engine status
- IFTA summaries
- Fuel transactions
- Messages and group messages
- Fleet info and fleet connections
- Workflows and execution events
- Resource operation events
- Users
TspEnum schema has also been updated to include rigbot as a valid enum value.Example response with RigBot as source:Affected schemas
The following schemas now includerigbot as a valid source_name value:
Need help?
API Reference
View complete endpoint documentation with current API structure
Contact Support
Questions about your integration? Our team is here to help