7

Every response from the API can be cached for up to a minute, so making the same request multiple times in that time-frame typically won't return different results. We make note of this in the throttle documentation: While not strictly a throttle, the Stack Exchange employs heavy caching and as such no application should make semantically identical ...


3

The link is correct. The purpose of that control is to provide a URL to the doc page with all the parameters prefilled. This is what most users expect and is similar to how that link control works on the rest of Stack Exchange. To get a direct link to the API, click on the link next to the Run button: This has a URL like: https://api.stackexchange.com/2....


2

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 behaviour is expected. This may change in some future release of the API, but the current behaviour is closer to the old on-site search approach, which only ever ...


1

Notifications typically contain links within their bodies. They're considerably more free-form than inbox_items, in that they're not typically attached to a post. Notifications only even have directly attached posts (at time of writing) in the bounty and edit cases. Note that if there's a post_id present, you can query /posts/{ids} to get a link. ...


1

The /search/excerpts route looks to be about as good as /search and it does return both questions and answers, and it does have an answers parameter. This route is "★ All new! For version 2.2! ★"


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