Hot answers tagged

5

Refer to the Stack Exchange API, Authentication docs. It looks like you are trying to authenticate using either a server you do not control, or a local server that is not on the public internet. Crucial Points: Do not specify a redirect_uri to any server that you do not control!!! When you use something like redirect_uri=https://www.yahoo.com/, then a ...


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


5

This doesn't have anything to do with Stack Exchange pages, it's a browser thing and mostly a very good thing. You can see that the page isn't doing it by: Disable all javascript on your browser. (Re)load an appropriate Stack Exchange page (or any long page with a <textarea>). Focus the textarea for keyboard input but use the mouse to scroll it out ...


4

The routes that don't link require POST requests because they create context, so there's nothing meaningful to be gained by going to those URLs in your browser. The rest of the routes return data when you send GET requests to them, which is why the link is useful in that case.


4

There's no real expectation set for this, feel free to pick whichever option seems better to you. I personally feel the tag is sufficient, but I could see how having it in the title might save some people some disappointment. My hope is that people will just finish their app and it won't matter much either way, so I'm not particularly concerned.


4

See the documentation for network_user.   top_answers and top_questions are not returned by default; you must specify them explicitly in a filter. When you ran /me/associated from the doc page and from your app, you used a filter (!-*f(6r3ZbZjn) that specified those two properties. When you used the address bar of the browser, you didn't specify a ...


4

items is documented in the Common Wrapper Object. It is an array of whichever object the given route returns. In the case of /me/associated,  items is an array of network_user objects. If you use a filter that returns .wrapper.type, then type will return the type that items has assumed. EG: { "items": [ // <=== Linked ...


4

You cannot do this. A delete feature has been requested and requested again (with status-planned given about 3.5 years ago). Register your desire for this by immediately upvoting these posts: Deleting an application key? How to delete an OAuth (2.0) API key? (Theoretically, if those feature requests get enough upvotes, they might get some developer ...


4

The API does not provide any method to determine a user's email address and it is unlikely to do so in the future. This would be a risk to both the user's privacy and his/her trust in Stack Exchange. And, a pressing need for this information has yet to be demonstrated, regarding the API. Note that Stack Exchange refuses to even provide the user's email hash ...


4

The various /questions routes do allow you to simultaneously retrieve answers, if you set the right filter. A good starting filter for getting questions with answers is: !gB7hjL3lhJ*Cnfe63rh6pAm74J(5qrOZKbL To Customize a Filter: Go to the /questions documentation page. Scroll to the Filter Edit Tool: Click on the tool and this dropdown appears: ...


4

Your stated problem is considerably easier than the question you linked. You can use the /users/{ids}/answers route to get what you want -- with a little work. The trick is to use a filter that returns the answers.tags property. In your case, if you really just want totals, and for one user at a time, you can use the filter: !GeF-5u(cSumXA . The ...


4

You can use /users/{ids}/associated Try it for your network account Returns all of a user's associated accounts, given their account_ids in {ids}. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for account_id on user objects. You can filter the network_users returned by this method with the types ...


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 &#39;.) 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 ...


3

The \r\n issue was solved when I changed to a POST request. But, since I was retagging questions (didn't really need to change the body, just resend it), I ended up using the body_markdown, encoded with HTMLParser.HTMLParser().unescape() body_markdown = str(HTMLParser.HTMLParser().unescape(question_data['items'][0]['body_markdown'])) And then sending ...


3

It sounds like you've either got a bug which is in fact making more requests than you think it is, or you're on a network where there's some other source of high-frequency requests. You're not supposed to have to deal with this situation in general, because this isn't an API error - it's an error from the load balancer because your IP is generating incoming ...


3

Notice that the route used has /top-answerers/. The doc page states: Returns the top 30 answer​ers active in a single tag, of either all-time or the last 30 days. (Emphasis added) So, that route is returning what it should. If you really want the top answers for a tag, use the /search/excerpts route and set: sort=votes order=desc ...


3

It's a bit confusing but that is not a bug. Think of it as, "Reputation change from when to when?" Since you specified neither a fromdate, nor a todate, you are effectively asking for the changes for all time. If you run the query for Nov 1, 2015 to Nov 9, 2015:           ...


3

Yes, I always get 86399 too. And, no, you can't specify an interval other than no_expiry. But you can call /access-tokens/{accessTokens}/invalidateDoc at whatever interval you wish. So, for less user annoyance, set no_expiry but then call /invalidate every, say, 8 days, for example.


2

The authentication process is described in the API docs: http://api.stackexchange.com/docs/authentication.


2

This is either a bug or an incomplete feature. See: What is the 'rev' dropdown supposed to do? Stack Exchange Revisions Dropdown Does Nothing? This extra dropdown seems to require: That the post have had previous edits. That the page mode editor is invoked. This editor is the default for low-rep users under at least some conditions. (low rep ...


2

No unnecessary parameters are required. order and sort are always optional. You can see this with these direct API calls: /2.2/users/5035500/questions?site=stackoverflow /2.2/users/331508/questions?site=stackoverflow It's hard to demonstrate a live link for /me/questions, since it requires an access token, but if you call that route from an app or ...


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


2

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.


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

Alas, no. The API currently does not have any easy way to track a user's edits. You can see what returns edit information by scrolling to the bottom of the revision object, documentation page. Currently, it says: Methods That Return This Type     posts/{ids}/revisions     revisions/{ids} Such cross-references are on every ...


2

First, you'll want to go upvote the feature request to add tag search for answers, etc. (If/when you have the upvote privilege) In the meantime, for answers by tag you can use the /search/excerpts route as long as you include is:answer in the q parameter. For example:       ...



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