Attach tags to a project
Attach one or more existing tags to a project.
Payload Requirements
tag_idsis required and must contain between 1 and 100 tag IDs.- Every tag must already exist and belong to the same space as the
project. A tag from another space returns
422. - Attaching a tag that is already attached is idempotent, so the same request can be retried safely.
- Unrecognized fields are rejected with
422rather than ignored.
Returns 200 with the project’s complete tag list, not 201: attaching
an existing tag creates no new resource.
Valid example
{
"tag_ids": ["VGFnOjEyMzQ1", "VGFnOjEyMzQ2"]
}
Invalid example (empty list)
{
"tag_ids": []
}
{
"type": "https://arize.com/docs/ax/rest-reference/errors#validation-error",
"title": "Unprocessable Entity",
"status": 422,
"detail": "tag_ids must contain at least 1 tag ID",
"request_id": "req_01HZY6X8E7"
}
Authorizations
Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format
Path Parameters
The unique project identifier (base64) A universally unique identifier (base64-encoded opaque string).
"RW50aXR5OjEyMzQ1"
Body
Body containing the IDs of the tags to attach to the resource
IDs of the tags to attach. Up to 100 per request. Tags must belong to the same space as the resource. Attaching a tag that is already attached is idempotent rather than an error, so the same request can be retried safely.
1 - 100 elementsA universally unique identifier (base64-encoded opaque string).
Response
Returns the tags attached to the resource
The tags attached to the resource, most recently updated first. Empty when the resource has no tags.
Pagination metadata. Tag lists are not paginated yet, so has_more is
always false and next_cursor is always omitted. The field is present
so that adding pagination later does not change the response shape.