Ordering on Paginated GET List endpoints

[BlankDev117]

trafficstars

It seems that responses in lists are not guaranteed to have a reproducible expected list. i.e. GET list for { a, b, c, d, e, ... } should return the order { a, b, c, d, e, .. } every response if pagination should work as expected.

In some tests locally, I've called and cached results from GET list endpoint for bills and it appears that I'm not getting a complete list by skipping to what remains (i.e. I pulled 250 on first call, 250 on second, etc., but despite this I don't have the entire unique data set and am lacking results).

If pagination is allowed, and requested, then results should have a well ordered response that is reproducible otherwise pagination doesn't make sense. If I might be misunderstanding the responses, please let me know, but my local tests aren't getting complete lists without going through the list endpoint entirely several times and given rate limits/locks, this isn't completely feasible for any congress session beyond the current one.

[rbram]

Thanks for reporting this issue. We’ll pass this feedback along to our developers.