Hot answers tagged

5

I don't believe that that route accepts POST requests (as it's non-actionable), so you should have better luck sending a GET request instead. Routes that require auth tokens necessitate HTTPS, but still expect GET for read requests, and POST for writes.


3

An inbox message body is not the same as a post body. Inbox messages are truncated by design. Here's a snippet of my inbox: Notice how the "body" is truncated at 100 characters? (Counting the ... and accounting for HTML entities like '.) The results I get from /2.2/me/inbox?filter=!SmOhH2b13NujlyyXX6 are exactly the same: "body": "Very ...


3

You should use /inbox instead, which is a network route instead of a site-specific one. As mentioned in the documentation, the site-specific route is mostly just provided for convenience of consumers working in a single-site context. Even then it doesn't seem particularly useful, but meh. To answer your question in regards to why site is required there, ...


2

There is no difference and... The inbox has always been "The global inbox". Certainly for as long as the API has existed. So any inbox route will be Stack Exchange wide, even if it accepts a site parameter. If you look at the doc for the /users/{id}/inbox/unread route, it says: This method is effectively an alias for /inbox/unread. It is provided for ...


1

Version 1.3 Update I have updated all the icons to make it look much better. You can check out the source code and download the DMG here: https://github.com/josephyoon/senotifier



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