Tag Management (v1 Only)

Notice

This document is a machine-translated draft and is currently undergoing review. Some content may be inaccurate or differ from the original Korean version. For the most precise information, refer to the Korean documentation.

Tag Management Feature Not Supported

• Scope of support: All endpoints related to tag creation/addition/removal/search are legacy features that were only available in v1, and have been completely discontinued in the v2 and v3 specifications.
• Migration recommendation: When migrating to v3, we recommend restructuring your system to use alternative business logic, such as assigning granular categories.

---

Retrieve content list by tag

• Original (v1): GET /media/tag/search/{tag}
• Changed (v2/v3): Not supported

Notable characteristics of the v1 response structure

The v1 response structure includes some edge cases that differ somewhat from the latest API standards. Please refer to this when analyzing the legacy system's response parser logic before migration.

• Missing message field: Only the { "error", "result" } structure exists, and the message field is not included in the response.
• Data type mismatch (count): The result.count value, which represents the total number of results, is returned as a string (e.g., "0") instead of an Integer.
• Inconsistency in nested array structure (items):
  • If one or more query results exist, the data is nested as an array object under items.item. ({"items": {"item": [...]}})
  • If there are 0 query results, the items key itself is returned as an empty array structure. ({"items": []})
• Response field types: Among the response data, original_file_size, status, and timestamp data are returned as Integer types, while audio_channel is returned as a Boolean type.
• Field name caution: The video frame count field name omits the underscore(_), appearing as video_framecount.

---

Add tag

• Original (v1): POST /media/tag/attach
• Changed (v2/v3): Not supported

Request body and response structure details

Request body

Field	Data Type	Required	Description
tag	String	Required	Tag string to add
upload_file_key	String	Required	Identifier of the content to which the tag will be added

Response structure specification

{
  "error": 0,
  "message": "success",
  "result": {}
}

---

Remove tag

• Original (v1): POST /media/tag/detach
• Changed (v2/v3): Not supported

Request body and response structure details

Request body

The request body specification is exactly the same as the Add Tag API.

Field	Data Type	Required	Description
tag	String	Required	Tag string to remove
upload_file_key	String	Required	Identifier of the content from which the tag will be removed

Response structure specification

As with the Add Tag API, an empty result object is returned upon success.

{
  "error": 0,
  "message": "success",
  "result": {}
}