Hot answers tagged bug
Fun one. Changes behind the scenes to how closed reasons are handled caused the API to stop getting a real reason and start getting a null one. This was just different enough from failing to get a reason that it went unnoticed, oy. This was fixed in the most recent build.
This has been fixed with the latest deploy. There was a bug introduced in our move to elastic search where min/max was applied after paging results, instead of before. This meant that in any question that would typically have a lot of out-of-range results, the first page would tend to be culled down to nothing.
Found it, fix has been deployed. There was a bit of confusion around loading tag data*, basically trying to get the "required", "mod only", and "sponsored" tags for api.stackexchange.com... which doesn't end well. *Data necessary for rendering revisions that have the [tag:name] markdown extensions.
This has been fixed in the latest deploy (it also affected body turns out). We've got some changes to our search infrastructure in the pipeline, and API v2.1 is being used to test them out. You might have noticed it's had some... issues. Better to find them in an API beta than after the rollout to the Q&A sites though.
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 single site rather than the Stack Exchange network as a whole. Since it's just more or less a convenience route for the global /inbox method, it doesn't actual ...
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: http://api.stackexchange.com/2.1/questions/13752517/related?site=stackoverflow
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 accordingly).
This has been fixed in a recent deploy, there were some errors calculating date ranges for those queries. As to "half a query"-type stuff, if there's literally no data for a day (which can happen, gathering query stats is sort of a "best effort" thing; it's rather rare though) our graph library will just interpolate. This can look a little odd. Note that ...
Only top voted, non community-wiki answers of a minimum length are eligible