tim.smith Team Lead, Lead Developer Evangelist
November 20

What's your use case for setting permissions via API when the conversation is not in queue? At what point are you trying to do this?


Visit Topic to respond.


In Reply To

Anthony_Gilio
November 20
Bummer. Thanks for the quick response. I'll see what is on the ideas portal.

Previous Replies

Anthony_Gilio
November 20

Bummer. Thanks for the quick response. I'll see what is on the ideas portal.

Jerome.Saint-Marc Genesys Employee
November 20

No. There is only this API endpoint, which can only be requested when the conversation is in queue.

Anthony_Gilio
November 20
Anthony_Gilio:

Anything that I can use that doesn't have that requirement?

Anything that I can use that doesn't have that requirement?

Jerome.Saint-Marc Genesys Employee
November 20

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,

Anthony_Gilio
November 20

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?


Visit Topic to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.