In the /tags route, the following information is returned for a specific tag:

  "name": "c#",
  "count": 262613,
  "is_required": false,
  "is_moderator_only": false,
  "has_synonyms": true

is_required indicates that the tag is part of the set of required tags for the site. This is great, but leads to problems when trying to indicate this using the data returned from the /questions route. The only data returned by this route is the tag name. Currently there is no method to fetch additional data for a specific tag.

  • 1
    Can't you just make another query to the /tags route?
    – Jonathan.
    Commented Feb 3, 2012 at 9:03

1 Answer 1


So... no, I'm -ing this. Fetching that sort of data for each tag on each question becomes unpleasantly slow when you're dealing with batches of questions (which most request are).

However, you are correct that there's no good way to grab additional data about a tag given just it's name. I've added the /tags/{tags}/info method to alleviate this.

For the specific "mimic the site styling" cases, I've added /tags/required and /tags/moderator-only. I suggest fetching and caching the result for quite a while (a day or even longer) since we rarely add or change either moderator or required tags.

on those. They've been deployed already.

Also, congratulations on getting what is probably the last V2.0 in. Feature freeze is fast approaching.

  • How does the /tags/{tags}/info method differ from the /tags with inname? Also why not just /tags/{tags} (not that I mind just should this method be used differently to others?)
    – Jonathan.
    Commented Feb 3, 2012 at 21:49
  • 2
    @Jonathan: I don't think inname allows for multiple tags. Commented Feb 3, 2012 at 21:52
  • Thanks for implementing this. Caching all tags is prohibitive, but caching only moderator or required tags is sensible. Commented Feb 3, 2012 at 21:53

You must log in to answer this question.

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