Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with inbox
Search options not deleted
user 7653
A question about the /inbox and related Stack Exchange API methods.
3
votes
Inbox item not marked as read after viewing
And neither the /me/inbox, nor the /notifications/unread docs claim to alter the state of the inbox items.
And, yes, that note seems to be misleading since the API does allow modifying comments. … For now, if you wish to avoid rereading "new" inbox items, you must track them in your app. …
- 13k
3
votes
Accepted
`body` of `inbox_item` returning only excerpt, not full body
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? … The results I get from /2.2/me/inbox?filter=!SmOhH2b13NujlyyXX6 are exactly the same:
"body": "Very good. I'm not an expert on user scripts after all. Good job.",
...
"body": "Aah, thnaks. …
- 13k
3
votes
Why is "body" missing from certain inbox items?
The documentation was updated sometime in the last 2 years and the API docs (version 2.2) now state that the property may be absent:
- 13k
2
votes
Accepted
Difference between `/inbox/unread` & `/me/inbox/unread`
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. … So we have:
/inbox/unread ~==~ /users/{id}/inbox/unread by "alias"
/users/{id}/inbox/unread ~==~ /me/inbox/unread by shorthand
So, /inbox/unread ~==~ /me/inbox/unread
Irregardless, they are de facto …
- 13k
2
votes
Are the inbox routes (`inbox_item`) missing some item types?
bounty_expires_in_three_days registration_reminder
bounty_grace_period_started reputation_bonus
edit_suggested substantive_edit
generic
So, you have to call both one of the /inbox … routes and one of the /notifications routes to get the same information that's in the Stack Exchange "inbox". …
- 13k