sender_id field on POST /v2/telematics/group-messages. The field is no longer required and now accepts multiple identifier types via anyOf, giving you more flexibility when creating group messages from systems that do not always have a Catena UUID for the sender.
Backward-compatible change: Existing requests that supply a UUID string for
sender_id continue to work without modification.Group message sender ID
What changed
Thesender_id field in the POST /v2/telematics/group-messages request body has been updated:
Previously,
sender_id was a required UUID string. It is now optional and accepts multiple identifier formats, allowing you to create group messages without a Catena-assigned sender UUID.
Affected endpoint
POST /v2/telematics/group-messages
Example usage
Create a group message without specifying a sender:Need help?
API reference
View complete endpoint documentation for the Telematics API
Contact support
Questions about your integration? Our team is here to help