3

Update: Op followed the advice, below, and changed the question from a bug to a feature-request. This is not really a bug. Right at the top of the API documentation, it states that the API is read-only, in bold letters: Stack Exchange API v2.0 This is the documentation for the v2.0 read-only (with optional authentication) Stack Exchange API. If ...


3

This is a bug. I've tagged your question accordingly. total, in the wrapper object, should always be the length of the items array, after concatenating all pages of results. When I run /2.2/notifications?pagesize=100&filter=!*L6X1NqVdlFobvlv, I get 4 pages of results, currently totaling 382 items: total remains fixed at 77. This is clearly a bug, ...


2

This is a very minor bug in the documentation page. The online doc page adds a convenient hyperlink to the post (The link part is not in the API's JSON response). That's a good thing. Most of the time this is rock solid, but notifications span all Stack exchange sites and the API doc pages normally only expect one site at a time. When the page is making ...


2

This is currently disabled on Firefox plug-in page: Mozilla.org > ADD-ONS > Extensions > Swatch Are there issues with this 'by-passing' controls, or allowing extra privileges?


2

This was fixed in the latest deploy. Sorry about the wait, a fix was actually staged a few days ago but deploying it was delayed by our yearly company get together.


1

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 ...


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