Hi Dragos,

Its not a bug,

I still wasnt able to test most of the calls but for the knowledge that I have of APIs, you have to implement a series of calls until you reach the last page.. you cant call all of them at once even if the limit variable is a 32bit integer, the api engine cant handle all at once (based on your tests looks like its 200).

So you have to do a loop of calls until the last page, the nextpage id is in each response.

RESPONSE:

{

"data": {

"devices": [

{...array_data...}

]

},

"paging": {

"size": 1000,

"pageId": "1",

"nextPageId": "2"

}

}

in this example you first call lets say with a limit of 100, the result is saing: (size:1000="there are 1000 devices in total in the group" but you will get the first "100", pageid=is the page you are and the next pageid. ). so in your calls should be:

/api/v1/device-groups/{groupId}/devices?limit=100

/api/v1/device-groups/{groupId}/devices?limit=100&pageId=2

/api/v1/device-groups/{groupId}/devices?limit=100&pageId=3

... and so on until lastpage.

Take a look at a diagram I made (attached).

PD. Im assuming that the variable "size" in the response is the total size of the call. ie. size=1000 but getting on blocks of 100.

Ref:

https://docs.ipswitch.com/NM/WhatsUpGold2021/02_Guides/rest_api/#tag/DeviceGroup

Best Regards,

Randol

Thanks Randol, that is the design of the apis. Paging allows the caller of the api to limit the amount of data it has to deal with and optimize the amount of data on the wire if they want. In turn, the back end has a maximum number of entries per page so no one caller can overwhelm the system, causing large transactions, memory or cpu use.