Skip to main content
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
Search options answers only not deleted user 4746

Indicates you've found an erroneous or unexpected behavior in the Stack Exchange API, or the Stack Exchange HTML or CSS, that needs to be fixed.

4 votes
Accepted

API returns implausibly low questions per minute rate for Stack Overflow

I mean, the value's not wrong, just perhaps not useful? The QPM is taken over the entire lifetime of the site, so 10005086 / 3644369.9112 = 2.745354133577943, where 3644369.9112 is ((Date.now() / 100 …
Tim Stone's user avatar
  • 4,676
2 votes
Accepted

What is the api_site_parameter of stackapps.com in API 2.x

It's just stackapps, although you can also pass in the full domain stackapps.com. The /sites route does indeed list StackApps, you just need to set an appropriately large page size (or page according …
Tim Stone's user avatar
  • 4,676
2 votes
Accepted

wrong results of /search/advanced

From the docs: Searches a site for any questions which fit the given criteria. (emphasis mine) The searches on the API aren't guaranteed to exactly replicate the current on-site search, so this …
Tim Stone's user avatar
  • 4,676
4 votes
Accepted

API docs titled "v2.0"; should be "v2.1"

That is the 2.1 documentation, it's just the title (and perhaps the first sentence) that hasn't been updated. All of the routes added in 2.1 are there, so you don't have to worry that it's missing an …
Tim Stone's user avatar
  • 4,676
1 vote
Accepted

Questions returned by /questions/{ids}/related do not contain link properties

The documentation you linked to is for API 2.x, but you're querying 1.1 which doesn't return those exact objects (and is deprecated). This API 2.1 request will return the results you were expecting: …
Tim Stone's user avatar
  • 4,676
1 vote
Accepted

Inbox and Notifications aren't being filtered by site

As described in the /me/inbox documentation, the route is ...effectively an alias for /inbox. It is provided for consumers who make strong assumptions about operating within the context of a singl …
Tim Stone's user avatar
  • 4,676
3 votes

How to deal with the "Too Many Requests" error coming as HTML?

It sounds like you've either got a bug which is in fact making more requests than you think it is, or you're on a network where there's some other source of high-frequency requests. …
Tim Stone's user avatar
  • 4,676
3 votes
Accepted

Is the display name meant to be escaped HTML in the 2.0 version of the API?

It's mentioned under the Safety section of the filters documentation that by default all response data can be safely inserted into HTML, which is why the data is pre-escaped in this case. You can try …
Tim Stone's user avatar
  • 4,676