a month ago - last edited 4 weeks ago by Mercedes_O
Hello! I'm using the vulnerabilities API and am having some issues when trying to page through records.
I'm sending the first page request with:
vulnerabilities (pagination: { limit: 3, page: FIRST })
And receive the following in the response:
"pagination": {
"page": "FIRST",
"next": "eyJvZmZzZXQiOjB9",
"limit": 5,
"current": "eyJvZmZzZXQiOjB9"
}
I then request the second page with:
vulnerabilities(pagination: { limit: 5, page: NEXT, cursor: "eyJvZmZzZXQiOjB9" })
And receive the following response:
"pagination": {
"page": "NEXT",
"next": "eyJvZmZzZXQiOjV9",
"limit": 5,
"current": "eyJvZmZzZXQiOjV9"
}
As far as I can tell, this is not behaving correctly as next and current should not be the same in the response each time? I've tested pagination with other endpoints and those do return different values for the next and current properties.
An additional oddity is that the total property is always returned as 0 despite records being returned.
Any idea what's going on with the pagination here?
3 weeks ago
Hello there!
Would you mind creating a support case so our integration team can have a look?
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now