conversations-v2

Released 2022-08-23Active

Migration Effort

Low

Estimated Hours

~4h

Primary risk if skipped: Incorrectly identifying or managing conversation resources, leading to API errors and potential data inconsistencies.

Breaking Changes2

fieldMediumConversations API

conversation.participants

The order of participants in the `conversation.participants` list is no longer guaranteed to be stable. Previously, it was sorted by `joined_at` descending. Now, it is returned in an arbitrary order.

Before

Participants sorted by `joined_at` descending.

After

Participants returned in an arbitrary order.

→

Remove any client-side sorting or reliance on the order of participants in the `conversation.participants` list.

endpointHighConversations API

/v2/Conversations

Resource names for Conversations and related entities (e.g., Participants, Messages) now include the Service SID. For example, a conversation resource name used to be `Conversation/<ConversationSid>`, and is now `Service/<ServiceSid>/Conversation/<ConversationSid>`.

Before

Resource names like `Conversation/<ConversationSid>`

After

Resource names like `Service/<ServiceSid>/Conversation/<ConversationSid>`

→

Update all references to resource names to include the Service SID, ensuring correct identification of resources.

Never get blindsided by an API change again

Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.

Join the Waitlist