7
votes
After successfully retrieving 180 pages, the API gracelessly, semi-silently, fails
Yes, this is a serious bug. You can replicate it from any browser using the code below.
Every time I run it, it fetches 180 pages at an average rate of 5.51 calls per second.
On the 181st call I get:
...
2
votes
Paging fails at 10K items for /search on any site but Stack Overflow
This was a search issue in elastic (max_result_window) that has now been tuned across the network.
See, also, this related Q&A on Meta SE.
1
vote
Accepted
How can I retrieve more than 25 pages from the Stack Exchange API v2.3?
Simply using an API key is enough to increase your quota from 300 to 10,000 per day, but it does not qualify as non-anonymous access.
The maximum page number that will be returned for anonymous API ...
1
vote
After successfully retrieving 180 pages, the API gracelessly, semi-silently, fails
This bug has actually been fixed, minutes after it was reported on MSE:
Thanks for reporting! A fix for this was just deployed, and the CORS headers are getting sent again.
A more detailed ...
1
vote
Accepted
The API is not returning a value that I know it should
The API results are paged, defaulting to 30 (base) records at a time.
So you need to always check the has_more property and fetch additional pages, if needed.
In your second query, it currently ...
1
vote
Accepted
Paging issue: is /users/{ids}/associated API route returning incomplete information?
No, this is not a bug.
When paging, you must remember and then combine the results from all pages.
So if you fetch:
/2.2/users/1144996;6913068;6453670;1751488;73042;1840350/associated?page=1&...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
paging × 10support × 5
api × 4
bug × 3
api-v2.2 × 3
status-completed × 2
search × 2
script × 1
feature-request × 1
users × 1
reputation × 1
api-key × 1
status-declined × 1
limits × 1
status-review × 1