PATCH /api/v2/conversations/participants/{id} ignoring custom attributes

Trying to update a participant’s custom attributes mid-call using the Conversations API. We need to push some CRM data into the session context for later reporting.

I’m sending a PATCH request to /api/v2/conversations/participants/{participantId}. The basic status updates (like status or muted) work fine. But when I add the attributes object, the API returns a 200 OK, yet the attributes never show up in the conversation history or the webhook payload.

Here’s the payload I’m sending:

{
 "attributes": {
 "crm_case_id": "12345",
 "priority": "high"
 }
}

I’ve verified the participant ID is correct and the call is active. I’m using the standard OAuth token for our integration app. Is there a specific schema requirement for the attributes object that I’m missing? Or is this endpoint strictly for status control?

The docs mention attributes are supported, but I can’t find any examples of them persisting through the call lifecycle via this specific endpoint.