Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It says no upvoted answers? Does that mean no accepted answers or no answers which have a positive vote? I'm kind of confused about the whole /answered result.

I'm trying to get questions with 0 answers using the API.

share|improve this question
up vote 1 down vote accepted

The documentation should be taken literally, i.e. your second interpretation no answers which have a positive vote is correct! This is in line with how the Unanswered tab is handled, see Why does the “Unanswered Questions” tab show questions that have answers?

I'm trying to get questions with 0 answers using the API.

You could start off from the /questions/unanswered route, from its result set you'll 'simply' need to filter out all those answers where the answer_count field is 0.

How 'simple' the latter really is depends on the client stack in use of course, i.e. you might be able to include the filter criteria in your request already, but otherwise you should always be able to search through the raw result array.

share|improve this answer
ok thanks, is there a way to search for questions with zero answers. Realy it would be great if you filter the API by any field the API returns. – Jonathan. Nov 29 '10 at 21:46
@Jonathan - that would be an obvious and welcome addition on the API level indeed; right now you'll need to do this manually or with the help of the particular client stack in use, see my extended answer on how to approach this. – Steffen Opel Nov 30 '10 at 0:46
The only problem with your extended answer is that if I download 25 questions sometimes there will be only 15 question truly answered other times there will be 20which is inconsistent. I could always over download but there'd be no guarantee and it use more bandwidth and time – Jonathan. Nov 30 '10 at 1:19
@Jonathan - indeed: there are several such limitations/shortcomings as of API v1 and quite some posts with similar issues accordingly; you'll have to ask the ones in charge for the API design (i.e. mainly Kevin Montrose) for the rationale in case, see e.g. his answer to Why is there no /answers route?; while I would have designed many things different myself as well, you'll need to account for this being a v1 - revisiting all these issues is one of the reasons why I recently asked about the API evolution ;) – Steffen Opel Nov 30 '10 at 1:51

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .