Tricky.

This was a consequence of the API misinterpretting a normalized field used elsewhere in the system to indicate whether or not a post has upvoted answers. Everywhere else we're using upvoted or accepted to mean "is answered", API wasn't doing the "or" check.

This was fixed in the last deploy.

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.

This was fixed in the last deploy.