Annotation Queues
Update an annotation queue
Update an annotation queue by its ID. At least one field must be provided.
Payload Requirements
- At least one of name, instructions, annotation_config_ids, or annotator_emails must be provided
- name must be unique within the space (409 Conflict if duplicate)
- annotation_config_ids replaces all existing config associations; all configs must belong to the same space as the queue
- annotator_emails replaces all existing user assignments; all users must have active accounts
Valid example
{
"name": "Updated Review Queue",
"annotation_config_ids": ["QW5ub3RhdGlvbkNvbmZpZzoxOmFCY0Q=", "QW5ub3RhdGlvbkNvbmZpZzoyOmFCY0Q="],
"annotator_emails": ["reviewer@example.com"]
}
Invalid example (empty body — no fields provided)
{}
<Note>This endpoint is in beta, read more here.</Note>
patch/v2/annotation-queues/{annotation_queue_id}
Path parameters
annotation_queue_idstring required
A universally unique identifier (base64-encoded opaque string).
Example:RW50aXR5OjEyMzQ1
The unique annotation queue identifier (base64)
Request body
Example request
{
"name": "Updated Queue Name",
"instructions": "Review each response for accuracy and helpfulness",
"annotation_config_ids": [
"ac_abc123",
"ac_def456"
],
"annotator_emails": [
"reviewer@example.com",
"annotator@example.com"
]
}Response
An annotation queue object
Example response
{
"id": "aq_abc123",
"name": "Quality Review Queue",
"space_id": "spc_xyz789",
"instructions": "Review each response for accuracy and helpfulness",
"annotators": [
{
"email": "user@example.com"
}
],
"created_at": "2024-01-15T10:30:00Z",
"updated_at": "2024-01-20T14:45:00Z"
}