Seeing Prime reporting 100APs for the API call. However today noticed that API Response says count 320 (# of APs) but lists only 100. Per the prime documentation, don’t see a way to retrieve all APs information. Here's the output response. Should the @last line say 320 and then show all 320 APs information.
API: https://10.211.29.107/webacs/api/v1/data/AccessPoints.json
Response:
{
"queryResponse": {
"@type": "AccessPoints",
"@rootUrl": "https:\/\/10.211.29.107\/webacs\/api\/v1\/data",
"@requestUrl": "https:\/\/10.211.29.107\/webacs\/api\/v1\/data\/AccessPoints",
"@responseType": "listEntityIds",
"@count": "320",
"@first": "0",
"@last": "99",
"entityId": [{
"@url": "https:\/\/10.211.29.107\/webacs\/api\/v1\/data\/AccessPoints\/476478",
"@type": "AccessPoints",
"$": "476478"
},
{
"@url": "https:\/\/10.211.29.107\/webacs\/api\/v1\/data\/AccessPoints\/476480",
"@type": "AccessPoints",
"$": "476480"
},
{
"@url": "https:\/\/10.211.29.107\/webacs\/api\/v1\/data\/AccessPoints\/476482",
"@type": "AccessPoints",
"$": "476482"
},
{
This is the API behaving as intended. By default, only the first 100 results are going to be shown. To show more results (up to a maximum of 1000) or to show subsequent pages, you must include paging parameters. Check out step 7 of the tutorial that we shipped in Prime Infrastructure 3.0. Alternatively, check out /webacs/api/v1/?id=paging-doc on your own server.
Comments
0 comments
Please sign in to leave a comment.