> ## Documentation Index > Fetch the complete documentation index at: https://docs.orq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Update an annotation queue > Partially updates an existing annotation queue. Setting `project_id` clears the legacy `human_review_ids` selection. **Related guide**: Annotations guide. See the [Annotations guide](/ai-studio/observability/annotations) for a walkthrough with examples. ## OpenAPI ````yaml patch /v2/annotation-queues/{annotation_queue_id} openapi: 3.1.0 info: title: orq.ai API version: '2.0' description: orq.ai API documentation servers: - url: https://my.orq.ai security: - ApiKey: [] tags: - name: Chunking description: Split text into smaller chunks for retrieval and generation workflows. - name: File Systems description: >- Create and manage persistent file systems that agents and MCP clients read from and write to. - name: Knowledge Bases description: Create and manage knowledge bases used by agents and retrieval workflows. - name: Memory Stores description: Create and manage memory stores, memories, and memory documents. - name: Evals description: Run an evaluator against a conversation and its result - name: Logs description: >- OpenTelemetry log query API. Search, filter, aggregate, and facet log records ingested via OTLP. - name: Reporting description: >- GenAI reporting API over canonical analytics rollups. Accepts a metric name, time range, grain, group-by, and filters; returns a typed time series and optional totals. - name: Traces description: >- Query and inspect ingested trace data: search trace summaries, aggregate metrics, and read individual traces and their spans. - description: List models available through the AI Router. name: Models - name: Policies - name: Alerts description: >- Alerts evaluate a Reporting API metric on a fixed interval and fire notifications through notifiers when the value breaches a threshold. Each breach opens a trigger that tracks the incident until the value recovers. - name: Annotation Queues description: Annotation queues collect spans for human review. - name: API keys description: >- API keys authenticate programmatic access to the workspace. They expose opaque tokens, per-domain access grants, and budget and rate-limit constraints. - name: Audit Logs description: Audit logs record workspace entity changes and access-relevant events. - name: Budgets description: >- Budgets govern spend, token usage, and request rate across six scopes: workspace, project, identity, API key, provider, and model. Every applicable budget is enforced, and the most restrictive limit applies per dimension. - name: Files description: File upload and retrieval operations. - name: Guardrail Rules description: >- Guardrail Rules conditionally enforce evaluators and plugins for AI Gateway traffic. Rules may be scoped to a project or the whole workspace. - name: Hub description: Hub items are reusable templates available to a workspace. - name: Identities description: >- Identities represent end users from your system for usage and engagement tracking. - name: Management keys description: >- Management keys are workspace-scoped credentials that authenticate programmatic access to workspace administration surfaces (API keys, budgets). Unlike project-scoped API keys, a management key always operates at the workspace level. - name: MCP Gateway description: >- Register upstream MCP servers, discover and sync their tools, and assemble gateways that expose a curated tool surface to MCP clients. - name: Model Catalog description: >- Browse the orq.ai model catalog: every model orq offers, across every provider, with pricing, capabilities and benchmark data. List endpoints only return models that are not deprecated. This API is public, requires no authentication, and is rate limited to 120 requests per minute per IP. Responses carry a 5-minute cache-control max-age. - name: Notifiers description: Notifier destinations used to send delivery and workflow notifications. - name: Projects description: Projects organize resources within a workspace - name: Routing Rules description: >- Routing Rules conditionally select models and enforce request plugins for AI Gateway traffic. Rules are evaluated by ascending priority and may be scoped to a project or the whole workspace. - name: Threads description: Threads group related trace invocations and their aggregate usage - name: Skills description: >- Skills are modular instructions you can use to codify processes and conventions - name: Smart Routers description: >- Create and manage workspace Smart Routers. A Smart Router selects a model from an eligible pool for each request according to a quality, balanced, or cost profile. - name: Webhooks description: >- Create and manage webhooks that deliver workspace events to external HTTPS endpoints. - name: Workspaces description: >- A workspace is the tenant. Create is called from a user session during onboarding; Get, List, and Update are the public management surface. - name: Workspace Security description: >- Workspace-level domain verification and IP allowlist controls. These operations are restricted to workspace administrators. - name: Workspace Settings description: >- Workspace-level settings managed with a workspace credential. A workspace is the tenant, so these settings are a singleton — there is nothing to create or delete, only read and update. - name: Responses - description: Run agents on a cron cadence. Minimum firing interval is 1 hour. name: Agent Schedules - name: Embeddings - name: Telemetry description: >- Unified query envelope for traces, metrics, and logs. One request shape, one filter dialect, and one response shape per source, validated by a per-source registry. - description: Beta. Run typed classification questions against a classify model. name: Classify - description: Search Gateway with managed credits or BYOK. name: Web Search externalDocs: url: https://docs.orq.ai description: orq.ai Documentation paths: /v2/annotation-queues/{annotation_queue_id}: patch: tags: - Annotation Queues summary: Update an annotation queue description: >- Partially updates an existing annotation queue. Setting `project_id` clears the legacy `human_review_ids` selection. operationId: UpdateAnnotationQueue parameters: - name: annotation_queue_id in: path required: true schema: type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/UpdateAnnotationQueueRequest' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/AnnotationQueue' x-code-samples: - lang: curl label: Core - Update an annotation queue source: | curl --request PATCH \ --url 'https://my.orq.ai/v2/annotation-queues/01HXXXXXXXXXXXXXXXXXXXXXXX' \ --header "Authorization: Bearer $ORQ_API_KEY" \ --header 'Content-Type: application/json' \ --data '{ "display_name": "Support quality review (Q3)", "description": "Updated review scope" }' - lang: python label: Python - Update an annotation queue source: | import os from orq_ai_sdk import Orq client = Orq(api_key=os.environ["ORQ_API_KEY"]) queue = client.annotation_queues.update( annotation_queue_id="01HXXXXXXXXXXXXXXXXXXXXXXX", display_name="Support quality review (Q3)", description="Updated review scope", ) print(queue.updated) - lang: typescript label: Node.js - Update an annotation queue source: | import { Orq } from '@orq-ai/node'; const client = new Orq({ apiKey: process.env.ORQ_API_KEY }); const queue = await client.annotationQueues.update({ annotationQueueId: '01HXXXXXXXXXXXXXXXXXXXXXXX', displayName: 'Support quality review (Q3)', description: 'Updated review scope', }); console.log(queue.updated); components: schemas: UpdateAnnotationQueueRequest: required: [] type: object properties: display_name: type: string description: Optional. New display name. description: type: string description: Optional. New description. project_id: type: string description: >- Optional. New project. Setting this clears the legacy `human_review_ids` selection. human_review_ids: type: array items: type: string description: >- Legacy: update manually selected human review IDs. Only applied when `project_id` is not set. AnnotationQueue: required: - _id - display_name - description - workspace_id - human_review_ids - metadata type: object properties: _id: type: string description: Unique annotation queue identifier assigned by ORQ. display_name: type: string description: The display name of the annotation queue. description: type: string description: The description of the annotation queue. workspace_id: type: string description: The unique identifier of the workspace it belongs to. project_id: type: string description: >- The project ID. When set, human reviews are resolved from the project automatically. human_review_ids: type: array items: type: string description: >- Legacy: manually selected human review IDs. Used only when project_id is not set. metadata: allOf: - $ref: '#/components/schemas/AnnotationQueueMetadata' description: Aggregate counters for the annotation queue. created_by_id: type: string description: >- The account that created the annotation queue. Unset when created via API key authentication. updated_by_id: type: string description: >- The account that last updated the annotation queue. Unset when updated via API key authentication. created: type: string description: The date and time the annotation queue was created. format: date-time updated: type: string description: The date and time the annotation queue was last updated. format: date-time AnnotationQueueMetadata: required: - items_count type: object properties: items_count: type: integer description: Number of items currently in the annotation queue. format: int32 description: >- Aggregate counters maintained by the service as items are added and removed. securitySchemes: ApiKey: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.