Tag Info

Hot answers tagged

7

You need to encode the # character (to %23) http://api.stackoverflow.com/1.0/questions?title=true&tagged=c%23


5

Not like this? http://api.stackoverflow.com/1.1/tags?pagesize=100&page=1 http://api.stackoverflow.com/1.1/tags?pagesize=100&page=2 ....


4

I agree. So it is written, so it is done. Behold, no wrapper posts.


4

the original question was apparently for V1. in V2 we now have https://api.stackexchange.com/docs/required-tags the request: https://api.stackexchange.com/2.0/tags/required?order=desc&sort=popular&site=stackapps will return required tags


3

I'm new to the API also, I think mostly multiple args are separated with ; Try c;java


3

That information is available in the /tags/{tags}/wikis route: "Returns the community editted tag wikis associated with a set of tags." Example: http://api.stackoverflow.com/1.1/tags/html/wikis


3

Related tags were one of the "maybes" slated for API V2.0. It got implemented today. Note that our definition of related is pretty much "appears on the same questions as", there's no real secret sauce there.


2

This has been fixed.


2

This should be fixed now.


2

Normally, I am the one arguing for more data but in this case I will anticipate (and agree with) Kevin's likely response: The tag meta is not relevant to a question and inclusion of tag meta would be a significant increase in response data as well as requiring an additional join into the tag table increasing the execution cost of generating the response. ...


2

Tags on the sites are, at most, 25 characters. Permitted characters are a-z 0-9 + # - . However, this is not part of the API contract insofar as if the site definition of a tag changes so will the API's. It is advisable, for correctness, to have a code path to handle tags > 25 characters in length. Simplest would be to truncate them. All that being ...


2

IIS ASP.net, by default, prohibits service of many file extensions, .cs is one. So the request is being killed by IIS ASP.net before it hits the REST handlers. This can be fixed fairly easily by striking the following entry, if so desired... %SYSTEM%\Microsoft.NET\Framework\v2.0.50727\CONFIG\Web.Config .... <httpHandlers> <add path="*.cs" ...


2

This has been fixed. There was effectively a missing where clause on that route. Very odd.


2

For those who prefer Opera, you can create a simple CSS file to auto-hide ignored tags (not just grey out those tags) ... .tagged-ignored { display: none !important } Call it SE.css and save it somewhere - then tell Opera to use it for your SE sites. (need to set it per SE site). Enjoy!


2

No, we won't be implementing this. Not that I don't see a use case for it, but we'd never be able to accept and execute arbitrary regular expressions against the database. It'd just be far too easy cripple performance wise (we've done this accidentally plenty of times, and we don't have to worry about malicious actors on the dev team). While we could ...


2

No, there's no API route that gives you a user's tag specific reputation information. The /users/{ids}/tags route only returns the combined count of questions and answers that a user has posted in a tag, but not the reputation information that you can get on the user profile tags tab. (Note: There's an app at Badge Status for a particular Tag in ...


2

As a result of some typos, those fields were being queried for... and then discarded immediately. A fix has been deployed.


2

The tag object now has a has_synonyms field which is true when there's at least 1 approved synonym for a tag.


1

To do this you have to use the /users/{ids}/answers path to download all of a user's answers, and then filter out the tags and/or tot-up the scores from there. Pseudo code: scoreByTag = [] // Empty associative array while (more pages of results) { 1) Fetch next page of answers 2) Store results and/or update scoreByTag array } Display/use select ...


1

For questions tagged with all tags in a list (AND operation), use the /questions path. For example: /questions#fromdate=2013-01-11&order=desc&sort=activity&tagged=ruby%3Bgit&site=stackoverflow&filter=default (Scroll to the bottom and press Run. See the top of the page for the documentation for that path.) ~~~~~ For questions tagged ...


1

Kevin was nice enough to grant my recent feature request on this endpoint, so it now returns "paged" results instead of a static top 30. I'm guessing the documentation just wasn't updated to reflect the change. I've tested it (StinkingBadges is using this functionality) and can confirm that your test result is the current "correct" behavior.


1

It's because tag ids aren't stable, so you can't reliably use them in the API. The same reason sites don't have ids. You'll note that most everywhere in the site's when we refer to a tag, we refer to it by name. Only when editing a few things do we expose the tag id, and those links can safely break.


1

Perhaps a good approach would be to cache the entire list of tags on a site (there are only 770, or 25 pages worth on Travel.SE). You can then run them through a RegEx locally. Tags don't change very much so you could just refresh your list every week or so to keep it up to date. You didn't specify a particular language / framework, but if you were using ...


1

Tag scores didn't really exist when v1.0 was released. They'll be in the next API version, barring any great difficulties in exposing them. Unfortunately the underlying data store has made this harder, not easier over time. Taking this off the planned list as that's no longer accurate.


1

Well, one of mine comes close... Stack2RSS converts an API request to an RSS feed that you can subscribe to with an RSS reader. (You can also get daily emails with the contents of the feed.) The RSS feed for tagged questions looks like this: http://quickmediasolutions.com/stack2rss/{site}/questions?body=true&tagged={tag} An example that fetches ...


1

Reputation gains from suggested edits are no longer returned by that route.


1

You can get that by using the questions/unanswered route with the tagged parameter.


1

The API supports the /search call, which only searches for an exact match within the title of questions. For more general searching, I believe the recommendation is to use a search engine. You can use their (Google, Bing, etc) APIs to search within a single site.


1

Its by design. Default order is descending across the board, this includes lexicographic sorts.



Only top voted, non community-wiki answers of a minimum length are eligible