Disconnecting from a call AND returning user routing status to IDLE

I am trying to figure out how to both disconnect a participant from a call AND return that user's routing status to IDLE from INTERACTING.

When I make the following API call, it successfully disconnects the participant from the call, but the user's routing status remains on INTERACTING, therefore they cannot receive additional call alerts, which is not the behavior we want.

PATCH /api/v2/conversations/chats/76c6044d-2e86-423f-9862-c70dd688ee6a/participants/69cdfa74-e033-4cc3-b10d-dc01fb707f26 HTTP/1.1
Host: api.mypurecloud.com
Content-Type: application/json
Accept: application/json
Authorization: Bearer ***
Content-Length: 29

{
  "state": "disconnected"
}

I observed the API calls that the Genesys Interaction Interface makes to end wrapup and therefore set the user's routing status back to IDLE, but making the same call from Postman or the API Explorer does not have the same effect. The user's routing status still remains on INTERACTING. Here is the API call I am making from Postman:

PATCH /api/v2/conversations/chats/76c6044d-2e86-423f-9862-c70dd688ee6a/participants/69cdfa74-e033-4cc3-b10d-dc01fb707f26 HTTP/1.1
Host: api.mypurecloud.com
Content-Type: application/json
Accept: application/json
Authorization: Bearer ***
Content-Length: 112

{
  "wrapup": {
      "code": "7fb334b0-0e9e-11e4-9191-0800200c9a66",
      "notes": "",
      "tags": []
   }
} 

Although this is the same call that seems to occur through the Genesys Interaction Interface, it does not seem to have the same effect.

I have also tried variations of the request body such as including "wrapupSkipped": true, but this does not have the desired effect either.

How can I disconnect a participant from a call AND return their routing status to IDLE so that they can continue to receive call alerts?

Resolved, the participantId in the call was the wrong one.