Search Results

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 …

It's getting to be that time (actually, it's about a month later than I'd hoped but still!), API V2.0 is shaping up and we're spending more and more time on UI polish rather than functionality. So let …

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 …

As has been announced, we're starting the public beta and spinning up a contest (as we did with V1.0). As such, some of the guidelines for the private beta no longer apply. The api-v2-beta tag no lo …

It's about time this thing got under way. If you're participating in the private beta, you should receive an email to that effect. If you were also a member of the V1.0 private beta, you'll notice w …

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 …

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 …

I'll slot this in for v2.1, not super useful in general but definitely interesting information that we should make available.

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 …

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 sp …

"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. Oftentime …

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_rema …

link is the best way to distinguish between items. No two items should have the same link, and inbox items aren't updated after they are created; they're snapshots of activity more than references to …

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.

When this class of error is encountered, the number of seconds until the quota rolls over is indicated as part of error_message now. For example: { "error_message": "too many requests from this app/ …