Is your conversation in a queue at the tie you sent the API Request?
If yes, that should work.

If your conversation is not in queue, then the request will fail.
It can only be requested when the conversation is in queue.

Regards,

Is there anything special I need to do? I have an active call the conversation clearly exists I can run the get conversation API etc but when I test this API I'm getting the following error:

{
"message": "Conversation XYZ does not exist.",
"code": "resource.not.found",
"status": 404,
"messageWithParams": "{entity} {id} does not exist.",
"messageParams": {
"id": "fbf09b5d-ee05-4abb-9799-540187e1ba22",
"entity": "Conversation"
},
"contextId": "e6a58f37-c7ab-48f2-80ae-e8ed57fa0ff6",
"details": [],
"errors": []
}

This one only functions while in-queue. Anything that I can use that doesn't have that requirement?

Hello,

That's correct.
This API endpoint will allow you to update attributes of an in-queue conversation. Supported attributes: skillIds, languageId, and priority.

Regards,

I believe this could be used please confirm
PATCH
/api/v2/routing/conversations/{conversationId}

We understand that a set skill action can be used while a conversation waits in a queue to add skills. We also recognize that you could perform this in a flow through a number attached to an external contact. We are looking for either the API being used for setskill action or an API that will allow us to do this in a live conversation. Hopefully, you can help.