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 |
This tag is for questions about the Stack Exchange API version 2. First released Feb 2012.
4
votes
Accepted
Why is my quota constantly decreasing?
I believe this was related to some other throttle/quota bugs that have been recently fixed.
Basically, some networking assumptions were incorrect, and a lot of apps ended up appearing to be coming fro …
2
votes
Accepted
Can you identify a user from the access_token?
The /me/associated routeDoc is the preferred way to turn an access_token into a list of users, it returns the collection of per-site user details that can be quickly fetched. It's basically the user' …
2
votes
"access_denied" error in the write answer at stackoverflow
You have to create a post describing your application, and edit it into your application's registration.
Basically, the first arrow needs a value; and you can set it when you edit (with the second …
3
votes
Accepted
API documentation pages match some site names incorrectly
The console JS was doing fuzzy matching on ?site; but that's not really correct, as you demonstrated.
With the latest deploy it does an exact match if possible.
5
votes
Accepted
Is there any support for Area 51 in the new API?
No, Area51 isn't in the API; it's different enough from the Q&A sites that it'd have to have a rather different one anyway.
There are currently no plans to make an Area51 API either.
31
votes
6
answers
2k
views
Draft Specification for API v2.0
We've started working on the next version of the Stack Exchange API.
The current draft specification is available, and we'd like to hear your feedback!
The headlining feature for this release is auth …
17
votes
2
answers
367
views
API Endpoint Changes Coming In Version 2.0
As work has progressed on the upcoming second version of our API, we've come to a bit of an impasse that's going to force a semi-radical change.
Here's the root of the issue:
once you've gotten an au …
3
votes
Accepted
Receiving error "Unexpected domain on proxy URL"
Your apps registered domain must match that the url passed as channelUrl.
You'll need to update your app's domain from actionbox.io to cybertron-nodejs-11139.apse1.actionbox.io (or whatever other ful …
1
vote
Accepted
Most of the url are missing the protocol
There was some monkeying around on the backend with URI generation, it's settled down now and this issue was resolved.
1
vote
Accepted
Support for OR constraint when querying questions based on tags
The tagged parameter to /search and related methods is an OR.
This query will return questions tagged c# or java, for example.
Or is rather expensive, which is one (of the many) reasons those method …
4
votes
Stack Exchange API is returning boolean(false) For 'is_answered' On Question With Accepted A...
Tricky.
This was a consequence of the API misinterpreting a normalized field used elsewhere in the system to indicate whether or not a post has upvoted answers.
Everywhere else, "is answered" is tru …
2
votes
Accepted
Stack Exchange API is returning non-existant/incorrect notices for questions
The bug here is that deleted notices were still being returned.
This was fixed in the last deploy.
2
votes
Accepted
Stack Exchange API is not returning the close vote counts for questions
This was fixed in the latest deploy.
4
votes
Accepted
The API has stopped allowing CORS requests
This was fixed in the latest deploy.
1
vote
Accepted
CDN redirect for the API's JavaScript SDK is incorrect
Naturally my first vacation in two years, and I break something right before going offline. Sorry about that.
This was fixed in the latest deploy.