Updating participant attributes during active voice call via API

Just noticed that writing to participant attributes during a live voice call seems inconsistent. I am using PATCH /api/v2/conversations/calls/{conversationId}/participants/{participantId}/attributes with a JSON body containing attributes. The call succeeds with 200 OK, but the values do not persist in the Architect flow immediately. Is there a delay in the attribute sync for voice channels compared to Web Messaging, or is the payload structure incorrect?

3 Likes