Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with paging
Search options not deleted
user 7653
For questions related to the use of paging (returning a limited number of results, and using a page parameter to get the next batch) in the Stack Exchange API.
1
vote
Accepted
The API is not returning a value that I know it should
However, in your first query, 46 records are available and, because you used the default paging of 30, only the first 30 are returned. …
- 13k
1
vote
Accepted
Paging issue: is /users/{ids}/associated API route returning incomplete information?
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? …
- 13k
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: …
- 13k