Since version 2.1, the answer object has a field called tags. However, sometimes, an empty array or even nothing is returned in this field:

Example with the filter !-*f(6t0Vk01e.

Am I doing something wrong or is this a bug?

1 Answer 1


This is a bug and seems (based on a series of A/B tests) to be linked with the body_markdown property.

That is, if your filter returns the tags array, it works:

"items": [ {
    "tags": [ "batch-file", "cmd" ],
    "answer_id": 42292030
  }, {
    "tags": [ "ios", "arrays", "swift" ],
    "answer_id": 42295110

, unless body_markdown is also selected:

"items": [ {
    "tags": [],
    "answer_id": 42295122,
    "body_markdown": "`ExecuteScalar` fetches the first column value of the first row. So, it won't make..."
  }, {
    "tags": [],
    "answer_id": 42294953,
    "body_markdown": "The git revert documentation provides the syntax like\r\n\r\n    git revert [--[no-]..."
  • 1
    Thanks! Hope this will be fixed, because I need body_markdown as well :-/
    – FelixSFD
    Commented Feb 17, 2017 at 10:42
  • 1
    was same problem (empty tags field) but solved with excluding share_link field from filter
    – Grundy
    Commented Dec 2, 2018 at 21:56
  • up_vote_count and down_vote_count also seem to have that problem. Commented Oct 24, 2021 at 12:37

You must log in to answer this question.

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