Tags can be attached to tickets and topics. Tags cannot be created or updated alone, but are always submitted in conjunction with create/update of an asset type.

List

GET /tags.(xml|json)
Returns the 100 most used tags. The list is updated once a day.

Response

Status: 200

<tags>
  <tag>
    <count type="NilClass">10</count>
    <id>63</id>
    <name>printer</name>
  </tag>
  <tag>
    <count type="NilClass">8</count>
    <id>62</id>
    <name>XP</name>
  </tag>
  ...
</tags>

List assets associated with given tags

GET /tags/#{tag}.(xml|json)?for=(ticket|entry)
Returns all assets associated with the given tags. Delimit tags with “+”. The list is paginated using offsets. If 15 elements are returned (the page limit), use ?page=2 to check for the next 15 and so on.

Response

Status: 200

<records>
  <ticket>
    ...
  </ticket>
  <ticket>
    ...
  </ticket>
  ...
</records>