Wrapup codes query returns partial results

[kpaull]

I ran this GET /api/v2/routing/wrapupcodes using api-explorer-standalone and received a partial list of our codes. The query returned a 200, successful operation. What am I missing?

I saw a reply by Tim somewhere else in the forum to use this: GET /api/v2/routing/queues/{queueId}/wrapupcodes I ran this and it wanted queueids. Can I feed a list of queue ids into it? If so how?

Thanks,

[Eos_Rios]

@kpaull

I ran this GET /api/v2/routing/wrapupcodes using api-explorer-standalone and received a partial list of our codes. The query returned a 200, successful operation. What am I missing?

Do you understand how to paginate?

@kpaull

Can I feed a list of queue ids into it? If so how?

It's DIY. You either manually do it or do it through a scripting language of your choice.

[kpaull]

Thanks Eos_Rios. As you can see I am new to this. I will look up paginate. Thanks for the DIY tip as well.

Cheers!

[John_Carnell]

Hi Kurtis,

Eos is right about using a scripting language to paginate on the API call. You can also use our Genesys Cloud CLI:

gc routing wrapupcodes list -a to dump all the routing wrapup codes without.

The -a tells the CLI to use auto-pagination for the query.

The CLI completely wrappers all of our API calls and can be useful for light scripting and system administration tasks.

Thanks,
John Carnell
Director, Developer Engagement