The categories API is identical for both Post categories, and Attachment categories, the only difference being the "type" parameter, which can be either "post" or "attachment".
For the full XML representation of categories, check out the data reference.
GET /categories/#{id}.xmlreturns a single category identified by its integer ID.
Response:
<category>
<name>Documents</name>
...
<category>GET /projects/#{project_id}/categories.xml(?type=[post|attachment])returns all categories for the given project.
To filter by type, pass the type parameter, which can be one of post or attachment.
Response:
<categories>
<category>
<name>Documents</name>
...
</category>
...
</categories>POST /projects/#{project_id}/categories.xmlcreates a new category of the given type for the given project.
The type attribute is required and must be one of post or attachment.
Request:
<category>
<type>post</type>
<name>Transcripts</name>
</category>Response:
Returns HTTP status code 201 Created on success, with the Location header set to the “Get category” URL for the new category. The new category ID can be extracted from that URL. On failure, a non-200 status code will be returned, possibly with error information in XML format as the response’s content.
PUT /categories/#{id}.xmlupdates an existing category identified by its integer ID.
Request:
<category>
<name>Transcripts</name>
</category>Response:
Returns HTTP status code 200 on success, or any other code (and possibly error information in XML format) on error.
DELETE /categories/#{id}.xmldeletes the category identified by its integer ID.
Note: that only categories without elements can be deleted.
Returns HTTP status code 200 on success. If the category contains elements a 409 status code (conflict) will be returned.