Hot answers tagged

5

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: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.stackexchange.com/2.2/tags?page=181&...


4

Just set pagesize in the URL, like: https://api.stackexchange.com/2.2/tags?pagesize=10&order=desc&sort=popular&site=stackoverflow


2

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

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 returns 22 records. So you see the "Meta Stack Overflow" result you expect. However, in your first query, 46 records are available and, because you used the ...


1

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&pagesize=100 and /2.2/users/1144996;6913068;6453670;1751488;73042;1840350/associated?page=2&pagesize=100 ...then combine the results you get all 36 sites ...


Only top voted, non community-wiki answers of a minimum length are eligible