After re-investigating my code, I realized what was going on here. For this particular project I wasn't using the API key and access token of my own application; I'm using the ones I sniffed from the communication between the Stack Exchange mobile app and the API. The Stack Exchange mobile app has an unlimited quota, it seems.
Yes, you can find out if the user has received the association bonus using the API. It's a bit clunky though.
However, as we discovered, "association bonus rights" are rather meaningless at the moment. Otherwise, you'd be able to edit wikis, upvote, comment, and flag on Information Security Stack Exchange right now, despite currently only having 1 rep ...
This is not the most educated answer, but through trial and error I have found a way to get the information I'm needing for my project. However, the biggest downside to this method seems to be the throttles that are in place. Websites like Codepen can easily exceed this, especially if you're using a debug window and a live/full screen view side by side for ...
In this URL: https://api.stackexchange.com/2.2/questions/unanswered/?team_url=stackoverflow.com%2fc%2ffoosite&site=stackoverflow&key=u9eRD30bklGv9t9gzDRSAQ(( you're passing a team_url parameter. That's not the right name, it should be team instead. You are passing the correct value.
This is a documentation bug in my opinion. The "via Example App" was never included, nor should it be.
A user is fully responsible for his or her content, it doesn't, and shouldn't, matter how that content was posted. Whether via: the web page, the Android App, a custom Stack App, or via Pony Express -- the content is what matters.
A rogue app would ...
I've just done a couple of tests with my placeholder app. Even though the question is closed, I was able to generate a new access token (following the regular procedure) for my sockpuppet account, and with it I was able to edit an answer in the Sandbox. The token for my regular account continues to work as well.
When the post is deleted, write access is ...
Here's a quick'n'dirty userscript, tested on Greasemonkey on Firefox: https://github.com/BobVul/SEReopenReviewWarning/blob/master/SEReopenReviewWarning.user.js
Can be installed via the raw link: https://github.com/BobVul/SEReopenReviewWarning/raw/master/SEReopenReviewWarning.user.js
Currently only the pending/completed review warning is there. I might add ...
I've been bitten by this feature as well in the past...
Responses from the API are compressed with GZIP (by default; you can request DEFLATE as well). Your browser automatically knows how to handle this; with most development libraries you have to specify explicitly that you want support for compression.
I don't have experience with the 'request' library ...
At the moment the number of tags allowed on a question is 5. Both client side and server side this limit is now1 enforced at the time of posting.
There is no direct limitation to allow 6 or even 7 tags. As a matter of fact, this query shows 1038 questions at the time of posting that have 6 tags. The revision for one occurrence reveals what caused that 6th ...
I don't think that's a bug, for implicit OAuth. Anyway, if I understand RFC 6749 correctly, that is not how you are supposed to do such extra checks.
Use the state parameter. And this works.
For example, a call to:
(Click the link and try it.)
Nope, that's the URL to the documentation, not the API endpoint itself. The correct one is
and you can find it by clicking on the link in the Try It widget:
I think creation_date is a default/universal sorting, unless activity_date is available. (But you know what they say happens when you "ASSUME".)‡
Seems like it would be required if paging is going to work well.
This post has 753 edits (759 revision entries) and the creation dates are all in descending order.
This post has 429 edits (...
So, you are making up to 150 requests in a 30 second period (10 "parallel requests", with a 2 second pause in between). And failing at 80 to 100+ seconds of operation and 400 to 500 total requests?
This other failure mode (NOT a 503) trips after about 32-ish seconds and 180 (sequential) requests.
It was previously reported that making about 2 calls per ...
You can filter (not sort) questions (and to some extent answers) by using the /search/advanced route of the API.
The q parameter allows most of the Advanced Search Options.
For example, this will fetch questions tagged python with at least 2 answers, and that have a score of 50 or more:
No, the API has a limited number of sort options (just like the website itself). The best you can do with the API is to fetch all results and then perform a client-side sort.
Alternatively, use SEDE which is much more flexible when it comes to sort orders, but it has the disadvantage of not providing real-time data. And it doesn't have an API, so it's only ...
Refer to the API Authentication docs; there are a great many things wrong with the URL in the question (at least 5).
For starters, it's to the wrong path. stackoverflow.com/oauth/authorize gives helpful messages/results like:
Oops! Something Bad Happened!
Authorization attempt not valid for current user
Authorization attempt unauthorized
I get the reason:
Do not use gem 'omniauth-stackexchange', '~> 0.2.1' ,but instead of gem 'omniauth-stackexchange', git: 'https://github.com/nashby/omniauth-stackexchange.git'
The reason see this:add call back url
No, there is no easy way to do this via the API.
Related feature requests:
Provide a method to search for sites winch merely wanted a search for site name/description. It was declined.
Search across Stack Exchange sites in Android app. To implement this usually would mean that a supporting method would be added to the API. This feature-request has been ...
I don't know about that Ruby/Gem, but your app registration is not correct.
You need to configure your app for explicit OAuth2, per this other answer, except enter localhost instead of example.com.
(The localhost is based on the original version of the question. If you have a registered domain, use that.)
Then, in your ruby code:
No there is no "Query API", especially not for SQL-like syntax.
It sure would be sweet to have an always current version of SEDE† (even if limited to, say, a hundred rows), but this is very unlikely to ever be provided.
Your options are:
Oftentimes the q parameter of the /search/advanced route is pretty powerful and will get you close to what you ...
While this isn't possible with the API, it is possible with SEDE, if you allow for up to 7 days of lag.
Here is the SEDE Query that lists Tag wiki and excerpts in descending edit date order:
when w.lasteditdate > e.lasteditdate
I am trying to get the amount of reputation that a user has
how to handle the response (or get one) from a script
You can do this with a Bash command that you can then embed in a script. Here's how:
1. Look up your user ID
Assuming you want to get the reputation on Stack Overflow, go to your account and look up your user ID in the URL:
There's unofficial collaborative Chat API Documentation for how everything in chat works.
Its split up into a couple different parts:
Receiving Events (Messages + other stuff)
More information here: Stack Exchange Chat API Documentation and Bot Boilerplate (finally)
Note: I started the ...