Take the 2-minute tour ×
Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. It's 100% free, no registration required.

When using the /questions/{ids} endpoint, the can_flag value for answers is never provided, even when specifying the option in the filter.

The can_flag for the question however, is populated.

Below is a JSON response for the API request:

https://api.stackexchange.com/2.2/questions/17264225?order=desc&sort=activity&site=stackoverflow&filter=!Odv4nK)K4FhSsUB)nx2J7RW6*YcmI9FslKzPFvMzpv3

... you'll obviously have to tack on your own key and access_token. The token I'm using in this instance has scope "no_expiry", "write_access", "private_info".

{
    "items": [{
        "answers": [{
            "downvoted": false,
            "upvoted": false
        }, {
            "downvoted": false,
            "upvoted": false
        }, {
            "downvoted": false,
            "upvoted": false
        }, {
            "downvoted": false,
            "upvoted": false
        }],
        "can_close": true,
        "can_flag": true,
        "downvoted": false,
        "upvoted": false
    }],
    "has_more": false,
    "quota_max": 10000,
    "quota_remaining": 9863
}

You can see that none of the answers has a can_flag attribute, whilst the original question does. By requesting the various downvoted, upvoted, can_close etc options, I'm trying to signify that my access_token does have permission to access the private data of the user in this example.

share|improve this question

You must log in to answer this question.

Browse other questions tagged .