Offset makes static lists API v1 endpoint unusable (can't paginate records for enterprise customer)
Hey folks,
We have a technical issue that currently affects 1 customer and it's not apparent from the API responses how to handle it (it might be an API bug).
A customer has more than 250 static lists. We try to paginate but the behavior of the offset is very strange.
With 3 records the endpoint always returns an offset of 12. Or 14 if we don't provide an offset. Or 1 if the offset is very high. Here are some example requests that we tried:
Offset makes static lists API v1 endpoint unusable (can't paginate records for enterprise customer)
Hey @Jaycee_Lewis, thanks for the welcome and for checking it :))
For your initial requests, are you sending a `count` and `offset`? Or just an offset?
Each code block examples starts with a piece of code that shows the URL that we are hitting, in both cases we are passing both.
What's the result and returned `offset` when you make use an initial request URL like this?
It's the same as not passing a count at all. The offset is 14 which to me seems pretty random given that in this dummy account we only have 3 static lists:
For this portal specifically, have you observed this issue with other endpoints or only with the static lists endpoint?
So far, we haven't noticed similar issues elsewhere, but we are also not paginating results anywhere else yet, I think.
Could you please confirm the language/library you are using to make these API calls? It looks like Ruby from the code snippets you provided, but I want to be certain😊
It is Ruby indeed with our self-rolled client 🙂 (no additional libraries/gems used)
For this portal specifically, have you observed this issue with other endpoints or only with the static lists endpoint?
Could you please confirm the language/library you are using to make these API calls? It looks like Ruby from the code snippets you provided, but I want to be certain 😊
Thank you very much for the additional information! — Jaycee