No page_number parameter in get_routing_queue_wrapupcodes

Hi,

We are having the same problem as defined in this post where we are trying to get all the wrapup code for a specific queue but can only get access to the first 25.

We can see in the response below that there are a total of 26 codes and 2 pages. We could use the next_uri to fetch the next page but that is not consistent with the majority of the other purecloud APIs we are using.

Is it now on the roadmap to support page_number and page_size as part of the request for get_routing_queue_wrapupcodes or we should instead look at next_uri for the time being.

thanks

          {'created_by': None,
           'date_created': None,
           'date_modified': None,
           'id': 'xxxxx',
           'modified_by': None,
           'name': 'SO-Verifiy Pending Order',
           'self_uri': '/api/v2/routing/wrapupcodes/xxxxx'}],

'first_uri': '/api/v2/routing/queues/xxxxxxx/wrapupcodes?pageSize=25&pageNumber=1',
'last_uri': '/api/v2/routing/queues/xxxxxxx/wrapupcodes?pageSize=25&pageNumber=2',
'next_uri': '/api/v2/routing/queues/xxxxx/wrapupcodes?pageSize=25&pageNumber=2',
'page_count': 2,
'page_number': 1,
'page_size': 25,
'previous_uri': None,
'self_uri': '/api/v2/routing/queues/xxxxxx/wrapupcodes?pageSize=25&pageNumber=1',
'total': 26}

That issue was closed due to the dev team being unable to reproduce. Please open a case with PureCloud Care and reference issue AS-1001 for escalation to dev. I've noted this forum topic in the issue as well. I believe I found the issue, but please open the case with care to help with prioritization of the fix.

I created an official ticket.
As always, thanks for quick answer Tim.

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