Search Results

I guarantee that if we did this, a large chunk of the developed apps would rely on /latest and break horrendously every time we rev'ed the API. The end user experience would be bad, developers would …

You've got this all backwards. Something being suitable for use on the sites is the first (not last) step in proving it's viable for inclusion in the API. The difference is, if something isn't working …

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 …

You can synthesize most/all of this call currently (new answers, changes in user rep, and comments directed at user are all accessible in v1.0) however it does take multiple calls. We'll revisit this …

Alright, here's what we're going to try. First off, we're not giving hard guarantees as to the maximum length of strings returned. Such a guarantee could create a situation where we might have to re …

API V2 did this, we send down: Access-Control-Allow-Credentials: false Access-Control-Allow-Methods: GET, POST Access-Control-Allow-Origin: * With every response.

Tag scores didn't really exist when v1.0 was released. They'll be in the next API version, barring any great difficulties in exposing them. Unfortunately the underlying data store has made this hard …

The problem with this isn't so much the security (though that's a concern), it's that we don't want the backwards compatibility constraints such blessed installations imply on our HTML and javascript. …

This is by design, for reasons of technical limitations. Unfortunately, we don't have easy access to display names at a "network level". What's available (and what's backing the API) is very normali …

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

This was dropped intentionally. The problem is that maintaining this sort of meta-api is both intensive (lots of v1.1 was spent not breaking v1.0 because of the way introspection was working) and of …

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 }, { "eve …

As with suggested edits*, tag wikis, privileges, and so on... we don't expose things in the API until they've settled down quite a bit. Also, "Whole network" APIs are something that take a bit of wor …

All write access is deferred until a future release, V2.0 is just adding authentication (and more read-only stuff, naturally).

You shouldn't be making more than 4 requests in this case. fetch a page of /users/{ids}/timeline group the ids by type (question, answers, comments) since the max pagesize fo users/{ids}/timeline i …