Hello!
I've seen in the API documentation that the /api/v2/routing/queues/{queueId}/users/ methods are deprecated, and it recommends to use /api/v2/routing/queues/{queueId}/members instead. However, I can't find any information about those endpoints.
Thanks!
Hi Adrian, I do apologize. We absolutely should have published information about the new endpoints! I have reached out the development team that owns these endpoints and have asked them to publish the new endpoints and provide documentation. I will reach out once this is done.
Thank you for the feedback!
-Becky
I spoke with our development team - the only change in the functionality of the endpoints is that GET /routing/queue/{id}/members does not return totals information (the total, lastUri, and pageCount fields) in its response. These fields will not be present at all in the new response. All other new endpoints function identically to what they replace.
We will get the docs updated ASAP - apologies again for any confusion we may have caused.
Best,
Becky
Ok, thank you Becky 
Hi Becky,
do you know when the new API will be available inside developer tool?
Best Regards,
Stefano Marciani
Hello
I would like to know when the methods will be available in the SDKs (at least, they aren't in the Python SDK current version)
Thanks
@Stefano_Marciani @Adrian_Santamaria The new APIs will be released in the API documentation, SDKs, and developer tools at the same time. Their release is currently in review, so they should hit production in 1-2 weeks.
Many thanks Tim!
You can code the new /api/v2/routing/queues/{queueId}/members API into a Call Data Action, I've already setup a new Call Data Action to replace the /User one for our customers that we do OnQueue Agent Count evaluation and routing for.
I wrote about it here - not sure that was the right place though 
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.