Tag Info

Hot answers tagged

5

No, the WebSockets are not officially supported. They are internal to Stack Exchange, use them at your own risk. If it is at all possible to do your task with the API, use that. That's what it's there for. Some people have sussed out some of the endpoints. You can see them in the answers to: How do the Stack Exchange WebSockets work? What are all the ...


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

There really is no particularly satisfactory way to do this since all versions of last_activity_date conflate a question's activity with the activity of its answers. You are going to have to fetch lots of items and filter out the chaff yourself. There are 2 main routes you can take, events or questions: A) Use the /events route: Use a filter that ...


2

You can use the /search method with tagged and intitle For example: http://api.stackexchange.com/2.2/search?order=desc&sort=activity&tagged=rest&intitle=api&site=stackoverflow will search for questions on Stack Overflow with api in the title and that are tagged with rest. The first two items I get when running this are: { "items": [ ...


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


2

You are probably having this error because of throttles (most likely per-method throttles) that are used to prevent abusive usage. Have a look at related documentation page in order to learn more about throttles. Normally you should wait for a specified period which is returned in the backoff field of the previous response.


2

Quoting from a comment of @BrockAdams to one of my answers, the preview parameter is used for development and testing purposes. If you set it to true, your request will only simulate whether it is a valid request or not and will not change anything on the site.


2

In order to get 50 questions for every request you need to pass pagesize parameter to your request URL. When you pass this parameter, you will need to pass page parameter to fetch the following pages. In order to exclude some attributes from the default set, you can use the "Try It" part of the documentation to create a filter for your specific purpose. ...


1

The answer to this question is the same to your other question about preview parameter. As @BrockAdams mentioned in a comment to one of my questions previously, you need to set preview parameter to true while testing write API calls. Please check the other answer for more information.


1

If you're trying some features right in the docs and this features require access token, it's requesting access to your token; if you approve, it appears as application. E.g., if you click "Get Token" button on the https://api.stackexchange.com/docs/notifications, you'll get: As for being listed it on Stack Apps: it isn't, as it's an app from SE.



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