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 ...
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, ...
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 ...
You can – sometimes. The default filter contains a question_id field, and according to the examples for the inbox_item type (you have to scroll down a bit) it is filled in some situations. I just tested it and the notification for this comment looks like this:
It should be populated for the new_answer type as well, but I couldn't test this quickly. It is ...
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 ...