Partner reference on Telematics write operations
A newpartner_ref field has been added to the request body and response schemas of all Telematics API write endpoints. This field lets you attach a partner-side reference identifier to each resource at creation or update time, making it straightforward to correlate Catena records with objects in your own system.
The change is additive and backward-compatible — existing requests continue to behave exactly as before.
Backward-compatible addition: The new
partner_ref field is purely additive. No existing integrations are affected.New field
Affected endpoints
POST /v2/telematics/dvir-logs
POST /v2/telematics/dvir-logs
The request body and all response schemas (200, 202, 502) now include a Example request body excerpt:
partner_ref field.POST /v2/telematics/fuel-transactions
POST /v2/telematics/fuel-transactions
The request body and all response schemas (200, 202, 502) now include a
partner_ref field.POST /v2/telematics/group-messages
POST /v2/telematics/group-messages
The request body and all response schemas (200, 202, 502) now include a
partner_ref field.POST /v2/telematics/messages
POST /v2/telematics/messages
The request body and all response schemas (200, 202, 502) now include a
partner_ref field.POST /v2/telematics/trailers and PATCH /v2/telematics/trailers/{id}
POST /v2/telematics/trailers and PATCH /v2/telematics/trailers/{id}
The request body and all response schemas (200, 202, 502) now include a
partner_ref field on both the create and update endpoints.POST /v2/telematics/users and PATCH /v2/telematics/users/{id}
POST /v2/telematics/users and PATCH /v2/telematics/users/{id}
The request body and all response schemas (200, 202, 502) now include a
partner_ref field on both the create and update endpoints.POST /v2/telematics/vehicles and PATCH /v2/telematics/vehicles/{id}
POST /v2/telematics/vehicles and PATCH /v2/telematics/vehicles/{id}
The request body and all response schemas (200, 202, 502) now include a
partner_ref field on both the create and update endpoints.POST /v2/telematics/workflows and PATCH /v2/telematics/workflows/{id}
POST /v2/telematics/workflows and PATCH /v2/telematics/workflows/{id}
The request body and all response schemas (200, 202, 502) now include a
partner_ref field on both the create and update endpoints.Need help?
API reference
View complete endpoint documentation for the Telematics API
Contact support
Questions about your integration? Our team is here to help