Legacy Dev Forum Posts

 View Only

Sign Up

/api/v2/routing/queues/{queueId}/users Deprecation Replacement

  • 1.  /api/v2/routing/queues/{queueId}/users Deprecation Replacement

    Posted 06-05-2025 18:18

    Jeremy_Gillip | 2021-03-01 21:04:51 UTC | #1

    I have been using the api /api/v2/routing/queues/{queueId}/users as an Genesys Cloud Data Dip lookup and i noticed on the replacement API /api/v2/routing/queues/{queueId}/members there is no "total": 1 or "pageCount": 1 when it returns the data. There has been a problem that i have to create one for each page 200 to check if there is more which is not ideal. Is there a reason that those totals are not provided on the members API?

    Thank you.


    anon11147534 | 2021-03-02 09:54:37 UTC | #2

    Hi,

    That's the pagination style the developers chose for this endpoint, I'm not exactly sure why they chose this style over the previous one. With this style, to determine if there are no more results there are 2 options:

    1. The nextUri value will be missing
    2. The entities array will be empty

    Jeremy_Gillip | 2021-03-02 13:14:58 UTC | #3

    Thank you for the feedback, I can pass a page field from the input of a flow i suppose and check the Nexturi has a value and loop it in Architect but was trying to avoid that to just get a number for a decision check.


    system | 2021-04-02 13:15:02 UTC | #4

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 10130