POST /v1/tags
Create a Tag
Create a new tag within a classification hierarchy with display name, description, parent relationships, and styling for data asset categorization using the Collate REST API.
POST
POST /v1/tags
Create a Tag
Create a new tag within a classification.Body Parameters
Name of the tag. Must be unique within the parent classification or parent tag.
Fully qualified name of the parent classification (e.g.,
Certification).Human-readable display name for the tag.
Description of the tag in Markdown format.
Fully qualified name of the parent tag for creating nested tags (e.g.,
PII.Sensitive).Visual styling for the tag.
Array of owner references (users or teams) to assign to the tag.
Provider of the tag:
user (custom) or system (built-in).POST /v1/tags
Returns
Returns the created tag object with all specified properties and system-generated fields.Response
Unique identifier for the tag (UUID format).
Tag name.
Fully qualified name in format
classification.tagName or classification.parent.child.Human-readable display name.
Description of the tag in Markdown format.
Visual styling for the tag.
Reference to the parent classification.
Provider:
user or system.List of owners assigned to the tag.
Version number for the entity (starts at 0.1).
Create or Update (PUT)
UsePUT /v1/tags instead of POST to perform an upsert. If a tag with the same fullyQualifiedName already exists, it will be updated; otherwise, a new tag is created. The request body is the same as POST.
PUT will not return a 409 conflict error if the entity already exists — it will update the existing entity instead. However, for certain fields (such as description, tags, owners, and custom properties), PUT preserves an already-populated value instead of overwriting it with an empty or omitted one — the exact behavior depends on the field and the calling user or bot’s permissions, not a blanket rule. See Entity Update Behavior for the full preserve/merge rules. Use PATCH to intentionally replace an existing value.