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


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


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


2

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


2

This seems to have been silently/magically fixed in the last 7 months (Date of Nicos Karalis' comment). Descriptions seem correct now. I had verified that they weren't correct when I upvoted this question on Apr 29 '14. Side note: It's not documented, but apparently tag-based badges are not listed unless they have been awarded at least once. Take a ...


2

bug support @Nathan Osman, I have been trying to get authentication working with your library (which is very useful BTW). However, whenever I use the explicit flow I end up with an error on the stack exchange.com/oauth/submit page saying: Cannot return to provided redirect_uri The uri I am attempting to provide is generated using BeginExplicitFlow in ...


1

Refer to the generic URI syntax, it is perfectly valid to have a fragment (The optional part of a URL that starts with an octothorpe #) without a preceding query (The optional part of a URL that starts with a question mark ?). This is how Stack Exchange returns tokens and other API's have used the same approach. There is nothing wrong with it. In fact, it ...


1

After all these years, it looks like this will never get implemented. However, it's not too hard to get the information via page scraping. From a browser or scraper that is logged in as the user, fetch the site's question page. (EG: http://stackapps.com/questions) Parse the #interestingTags > a.post-tag nodes. For example, this javascript will work ...


1

Although this can be annoying or confusing, there is no bug. Take a look at your Stack Exchange accounts page. Currently it shows: (Click for larger image) 10 questions, here on Stack Apps, and 1 question on Stack Overflow. Those are the same numbers currently reported for you by /users/{ids}/associated. Both sets of numbers are currently stale (You ...


1

Here is a small script (stackprinter) which uses Stack Printer from the command-line: #!/bin/sh type wkhtmltopdf || { echo >&2 "wkhtmltopdf command is required. Aborting."; exit 1; } : ${1?"Usage: $0 (url)"} URL=$1 && shift HOST=$(echo $URL | egrep -o "([.[:alnum:]]*?)\.(com|net|org)" | head -c-5) QID=$(echo $URL | grep -o "\d.*/" | head ...



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