Provider verification - 400 on PATCH /api/v2/conversations/{conversationId}/participants/{participantId

We’re gettin’ 400s in teh Pact pipeline - provider’s rejectin’ a PATCH to update a participant’s state. It’s the standard endpoint - /api/v2/conversations/{conversationId}/participants/{participantId}.

The consumer’s sendin’ a JSON payload lookin’ like this:

{
 "state": "DISCONNECTED"
}

SDK version is genesys-cloud-platform-sdk@4.1.1. Flow’s just callin’ the API directly - no data actions. It’s been receivin’ failures for like an hour.

The provider’s response body is just: {"message":"Bad Request","code":"BAD_REQUEST","phrase":"HTTP 400 Bad Request"}. No details.

Seems like somethin’ changed on the API side.
S