Hot answers tagged api-v2
10
Move the id value into the query string
In that the id is vectorized, it is designed to represent multiple values.
Currently the id field is a component of the url. This severely constrains the number of records that can be retrieved far below the stated maximum of the max pagesize which is 100.
Another, more serious, implication of this limitation is ...
10
Just wanted to let everybody know that I just made a new release of the library here. This release includes tons of bug fixes as well as some breaking changes which shouldn't be a problem if you have been running off the trunk.
Also, by popular demand, I added a .Net 3.5 version of the library to this release. The hope here is to eventually have a mono ...
9
User Authentication
This is an obvious one (and a stated goal for V2, I think).
The basics would be for some way to authenticate a user against his StackOverflow/etc user. Also, a way to access the "linked accounts" information would be great (so authenticating a StackOverflow user will automatically give the application knowledge of his other accounts ...
7
EDIT: Implemented using Web Sockets (because the caching characteristics of the API does not allow real-time notifications). I created a Chrome extension and Firefox add-on, and created a Stack Apps listing at Real-time desktop notifications for Stack Exchange inbox.
In Google Chrome, the popup is closed when performing an action outside it (clicking, ...
7
I updated several aspects of the app in response to user feedback:
Error handling is somewhat better (it will now tell you if your token is invalid, instead of a generic "error" alert)
Queued API calls are aborted now, which should speed up site changing, among other things.
There's now an option to deauthorize the app, should you decide to revoke its ...
6
For /sites (and only it) I have removed the pagesize constraint.
I believe in this case it makes sense, since applications are expected to query all of that data and cache it for long periods of time. The constraint remains elsewhere, as it's very important for performance reasons.
5
Addons
Stackprinter allows you to print directly from Stack Exchange sites using Greasemonkey script or an handy bookmarklet.
Greasemonkey script adds a Printer-Friendly button to the question you are browsing (Firefox and Chrome both supported).
Bookmarklet is useful if Greasemonkey is not an option and has the same effect of Printer-Friendly button, ...
5
"Agile" API releases are a really bad idea, frankly.
The StackOverflow code base undergoes rapid iteration already, just watch the build numbers. On average we deploy at least once a day. Oftentimes these are just bug fixes, but a non-trivial amount of the time we're introducing new features or revising existing ones.
To take one feature for example:
...
4
the original question was apparently for V1.
in V2 we now have https://api.stackexchange.com/docs/required-tags
the request: https://api.stackexchange.com/2.0/tags/required?order=desc&sort=popular&site=stackapps will return required tags
4
Thank you!
All of the new changes are welcome and I can't wait to start implementing some of them in my apps.
I do have one question though: what happened to all of my apps? I had a thumbnail image set for all of them and it doesn't look like any of them are being displayed despite matching the requirements (144x119 in PNG format).
Edit: This doesn't ...
4
Whelp, that was an oversight.
accept_rate should now be returned on both user and shallow_user. Note that when insufficient data is available to calculate an accept rate, we don't return anything at all.
The exact rules for calculating accept rate are subject to change, but currently documented here. The API returned accept rate should always match the ...
4
I don't follow, for date times the most recent date is the largest date.
Sample return by events
{
"event_type": "question_posted",
"event_id": 9369546,
"creation_date": 1329777738
},
{
"event_type": "comment_posted",
"event_id": 11832402,
"creation_date": 1329777736
}
1329777738 => Mon, 20 Feb 2012 22:42:18 GMT
1329777736 => Mon, 20 Feb 2012 ...
4
See the "Safety" heading in the "Custom Filters" doc. The difference between a "safe" (default) filter and an "unsafe" filter, is that the unsafe data might return data that could result in a script injection if the data was directly inserted in an HTML document. (EG: '<script src="PwnYaSucka.com">...')
Some fields are apparently inherently devoid ...
3
I'm going to lay some ground work about authentication and access tokens before answering, because I think you have some misconceptions.
When a user authenticates an application they have given permission for it to access their data in certain ways (via scope). The actual mechanism* for accessing this data is an access token, but the authorization to get ...
3
With the way the API is currently set up (lots of caching the info page says) is it possible to update the information on a question you've already looked at? I have a list of questions but, as time goes on, the information changes (# of answers, votes, etc) and I would like to be able to update the questions with the new info.
3
UPDATE
I've made some improvments:
You can now monitor
meta.stackoverflow and stackapps
You can choose on the options page
whether you only want to see
questions that contain ALL of the
tags you specified or to show
questions that contain ANY of the
tags (like SO's Interesting Tags
feature)
I've made some stylistic changes to
the options page (fonts, CSS, ...
3
Mkay, I've only used the part of the code that relates to StackAuth:
You forgot to update the version number for SitesMethod and UsersByIdAssociatedMethod
SitesMethod and UsersByIdAssociatedMethod both take $key as a parameter, but seeing as we've already inited the stackPHP object with the key, seems a bit redundant. I changed my SitesMethod function to ...
3
The API now responds with the following headers:
HTTP/1.1 200 OK
Server: nginx/0.7.65
Date: Fri, 20 Jan 2012 18:53:44 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Cache-Control: private
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST
Access-Control-Allow-Credentials: false
Content-Length: 12345
Since we ...
3
It's mentioned under the Safety section of the filters documentation that by default all response data can be safely inserted into HTML, which is why the data is pre-escaped in this case. You can try creating an unsafe filter using the unsafe parameter to use if you wish to avoid this conversion.
3
Filters are created by sending include, exclude, and base to /filters/create. You can use GET for rapid prototyping, or POST when the amount of data you're sending grows too large for a GET.
base specifies a filter to use as a template. It is the "default" filter, by default. A blank slate can be achieved by using "none".
include and exclude contain ...
3
i have a doc scraper that produces json schema and smd. eventually it will be published as a service on SOAPI2.com, much the same way that soapi.info provides meta for v1.
but until then you can find the meta files here: https://github.com/bitpusher/SOAPI2/tree/master/src/SOAPI2.DocScraper/js
this meta is what i generate routes and model for soapi2 from, ...
3
If you visit:
http://stackapps.com/edit-tag-wiki/codeigniter
... you're redirected to that URL. If you don't mind the redirect, you might just be able to get around it that way.
As far as I know, there's no documentation about when you can specify a name versus when you must specify an ID number, and I know of no API route that returns the ID numbers. ...
3
Yes, you can change very nearly everything (and actually everything that's user entered) about an application after it's been registered.
You should use the domain you intend to host the client-side app under as your OAuth Domain. While not strictly necessary, it's the sanest option.
3
I think Py-StackExchange is your best bet; there's an API V2.0 branch that seems to be active.
3
Found it, fix has been deployed.
There was a bit of confusion around loading tag data*, basically trying to get the "required", "mod only", and "sponsored" tags for api.stackexchange.com... which doesn't end well.
*Data necessary for rendering revisions that have the [tag:name] markdown extensions.
3
To find user_id(s) for a username, use the inname parameter of the /users query.
You will have to repeat this query call for every Stack Exchange site that you are interested in. For example:
/users?inname=Zagorulkin&site=stackoverflow&filter=!6Xcz2tYayQsZ1
/users?inname=Zagorulkin&site=programmers.stackexchange&filter=!6Xcz2tYayQsZ1
If ...
3
This has been fixed with the latest deploy.
There was a bug introduced in our move to elastic search where min/max was applied after paging results, instead of before. This meant that in any question that would typically have a lot of out-of-range results, the first page would tend to be culled down to nothing.
2
Not sure if this is the right place for it, but I'm having some issues when I try and deploy this wrapper on a server as opposed to my local environment.
First of all, I don't have SQLite3 on my server and do not have the ability to install it so I've set the caching to 0.
Second, I have got it working perfectly on my local dev server that has internet ...
2
For native applications (ie. Desktop apps), in order to participate in an OAuth 2.0 flow you need to embed a browser control (or otherwise instrument one so you can read the current location, including hash) and do an implicit (ie. Client Side) flow with a redirect_uri of https://stackexchange.com/oauth/login_success. When you detect navigation to that url, ...
2
Each application/user pair (as signified by an access_token) has a per-day quota of 10k requests (by default). Any number of these can be in flight at once, and they're reported as part of quota_remaining and quota_max.
On top of that, is a per-user quota of 50,000. This quota isn't reported anywhere (for privacy reasons, we'd rather not leak a user's ...
Only top voted, non community-wiki answers of a minimum length are eligible
