Tag Info

Hot answers tagged

11

It could be a proxy between you and the API that is mangling the headers that are being sent and making the request without compression. This is one downside to mandatory compression. It might be nice if there was an https endpoint that could be hit to test these types of issues or even to fall back to. If the point of mandatory compression is to save ...


9

I agree that there needs to be a way to discover API endpoints. Especially with the brave new world of SE 2.0 potentially leading to an ever increasing number of API-ified sites out there. However, there isn't a good place to shove this functionality just yet. Currently, we only have two places it could go: ...


8

This is a tricky one, and I can't really say how it will be solved in the future but we'll have to figure out something. The inability to render questions is kind of a major deficiency (if one that didn't exist until well after 1.0 was frozen). This has been added in 1.1. /1.1/sites reports markdown_extensions with values Prettify, MathJax, and jTab as ...


7

Its 10k now, the way it was intended. Anyone with an active lease will stick to 100k until the day ends, or an update is deployed.


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.


6

Oy, that was an annoying one. Subtle, as the bug only happened when you're not logged in but would be automatically logged in when you visit stackexchange.com. The actual root cause was just over-encoding a url.


5

This is important if you want to be able to build an app that supports all available sites. Right now there are only a few, but eventually the list will grow and simply adding entries by hand will become too difficult. There also was a similar request for discovering what versions of the API are available. The tricky part is that the methods would not ...


5

This would be a good idea, as it would immediately clue developers into the resources that are here specifically to make the API easier to use.


5

pagesize=0 is now permitted. You can use this to get total on all the methods that support paging, generally very quickly.


5

The icon_url images returned by StackAuth (and /stats) should all now have transparent backgrounds.


5

Thanks for this, I like it. The proposal's style is as clean and polished as other state of the art marketplaces; here are some screenshots: Apple Google Microsoft Mozilla On your proposal I would add: Authors: I like what Mozilla does, Author should be displayed. Votes: we don't have number of downloads or shiny stars. Votes number is our rating ...


5

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 ...


5

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.


4

I totally agree: Discussion: dialog revolving around a topic Support: a request for assistance or clarification discussion != support


4

Anything that supports a sort of activity can do this already. ?sort=activity&min={start-date}&max={end-date} Where start-date and end-date are unix timestamps. Update /questions and /questions/unanswered now honor min, max, and order. sort | min and max limit -------------------------------- active | last_activity_date newest | ...


4

Search intitle is now case insensitive.


4

I wish I could blame a failed blow out preventer - fixed :)


4

If your [app] isn't available at the end of the day tomorrow, its not getting considered. The cutoff is the start of "the first week of August," so you have (roughly) until its August 1st or later across the entire Earth.


4

We're fixing this, shouldn't be too much longer (may even have been done by the time you read this). Basically, this is another consequence of using a cloud computing service. We've got a bunch of crummy (and technically illegal, due to attribute violations) sites out there that like to scrape us. Now, we realize its a fools errand to try and prevent ...


4

Anything we should be showing and aren't? Attribution (i.e. keep the author name/link) My vote would be to drop the noisy reputation and last update time indeed, but keep the author name/link in the bottom right corner still, albeit with substantially reduced color/contrast (e.g. the last update color currently in use would probably do just fine): ...


4

ASP.NET was freaking out about the < in your search term. Fixed it*. More generally, the API always returns compressed content; so everything is "binary," this case just showed it more obviously due to the unusual error. *It's worth noting that the actual < and > are not indexed by our Lucene search provider, so you can't actually search for ...


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

These typos were fixed in the latest build.


4

This will be fixed in the next build.


4

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 true if either of the following are met: The question has an accepted answer The question has an answer with a score > 0 The API wasn't doing the "or" check. ...


3

This will be ready on the next deployment of the API.


3

Kevin hinted at something like this when I was discussing making a FUSE (file system in userspace) implementation of the API on dev.meta. It would work like this, assuming you had the file system mounted on /stacks : cat /stacks/stackoverflow.com/users/1/reputation ... You'd see Jeff's reputation. The problem is (and was) is that I'd need to be able to ...


3

I think www.stackapps.com should be redirected to stackapps.com, currently can see the same page but cookies validation looks failing


3

No need, the "apps" tag pulls anything tagged "app" or "library" already. Alternately, just click library and browse all the libraries. (sorry, this change has been in for a while, we just hadn't deployed.)


3

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 release an API revision just to accommodate increased text limits on the trilogy sites, or one - which is equally bad - where the API would return truncated ...



Only top voted, non community-wiki answers of a minimum length are eligible