> ## Documentation Index > Fetch the complete documentation index at: https://docs.avidoai.com/llms.txt > Use this file to discover all available pages before exploring further. # Get all document IDs > Fetches all document IDs without pagination. Supports filtering by status and tags. Useful for bulk operations. ## OpenAPI ````yaml https://app.stainless.com/api/spec/documented/avido/openapi.documented.yml get /v0/documents/ids openapi: 3.1.1 info: title: Avido API description: >- Avido's API for LLM usage events, tool calls, trace management, webhook validation, and more. See each endpoint's request/response schema for details. version: 0.1.0 contact: name: Avido Support email: support@avidoai.com url: https://avidoai.com/support servers: - url: https://api.avidoai.com description: Production API security: - ApiKey: [] ApplicationId: [] paths: /v0/documents/ids: get: tags: - Documents summary: Get all document IDs description: >- Fetches all document IDs without pagination. Supports filtering by status and tags. Useful for bulk operations. operationId: listDocumentIds parameters: - in: query name: type schema: default: KNOWLEDGE description: Filter by document type. Defaults to `KNOWLEDGE` when omitted. example: KNOWLEDGE type: string enum: - KNOWLEDGE - POLICY description: Filter by document type. Defaults to `KNOWLEDGE` when omitted. - in: query name: documentStatus schema: description: >- Filter by document-level status (`DocumentV2.status`). When omitted, the API defaults to `ACTIVE` for library queries and skips the filter for quickstart-scoped queries (so DRAFT KB-Review uploads remain visible). Distinct from `status` below which filters the document's active version status. example: ACTIVE type: string enum: - DRAFT - ACTIVE description: >- Filter by document-level status (`DocumentV2.status`). When omitted, the API defaults to `ACTIVE` for library queries and skips the filter for quickstart-scoped queries (so DRAFT KB-Review uploads remain visible). Distinct from `status` below which filters the document's active version status. - in: query name: status schema: description: >- Filter by document version status (filters documents by their active version status). Supports multiple values. example: APPROVED type: array items: type: string enum: - DRAFT - REVIEW - APPROVED - ARCHIVED - ACTIVE description: >- Status of the document. Valid options: DRAFT, REVIEW, APPROVED, ARCHIVED, ACTIVE. example: APPROVED description: >- Filter by document version status (filters documents by their active version status). Supports multiple values. - in: query name: tagId schema: description: Filter documents by tag ID example: 789e4567-e89b-12d3-a456-426614174000 type: array items: type: string description: Filter documents by tag ID - in: query name: search schema: description: Search in document version title and content example: API documentation type: string description: Search in document version title and content - in: query name: scrapeJobId schema: description: Filter by scrape job ID. Supports multiple values. example: 321e4567-e89b-12d3-a456-426614174000 type: array items: type: string format: uuid pattern: >- ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$ description: Filter by scrape job ID. Supports multiple values. - in: query name: fileProcessingId schema: description: >- Filter by source FileProcessing ID (the row that ingested the doc). Supports multiple values, capped at 100. example: 654e7890-e89b-12d3-a456-426614174000 maxItems: 100 type: array items: type: string format: uuid pattern: >- ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$ description: >- Filter by source FileProcessing ID (the row that ingested the doc). Supports multiple values, capped at 100. - in: query name: topicId schema: description: Filter documents by topic ID example: 789e1234-e89b-12d3-a456-426614174000 type: string format: uuid pattern: >- ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$ description: Filter documents by topic ID - in: query name: assignee schema: description: Filter by assignee user ID example: user_123456789 type: string description: Filter by assignee user ID responses: '200': description: List of document IDs retrieved successfully content: application/json: schema: $ref: '#/components/schemas/DocumentIdsResponse' examples: basic: summary: All document IDs value: documentIds: - 123e4567-e89b-12d3-a456-426614174000 - 223e4567-e89b-12d3-a456-426614174001 - 323e4567-e89b-12d3-a456-426614174002 filtered: summary: Filtered by status value: documentIds: - 123e4567-e89b-12d3-a456-426614174000 - 223e4567-e89b-12d3-a456-426614174001 '400': description: bad request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: invalid input content: application/json: schema: $ref: '#/components/schemas/ValidationErrorResponse' '500': description: internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: DocumentIdsResponse: type: object properties: documentIds: type: array items: type: string format: uuid pattern: >- ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$ description: Array of all document IDs matching the filter criteria example: - 123e4567-e89b-12d3-a456-426614174000 - 223e4567-e89b-12d3-a456-426614174001 - 323e4567-e89b-12d3-a456-426614174002 required: - documentIds additionalProperties: false title: Document Ids Response description: Response containing all document IDs without pagination ErrorResponse: type: object properties: message: type: string description: A human-readable error message explaining the error. example: Resource not found required: - message additionalProperties: false title: ErrorResponse description: Standard error format for failed API operations. ValidationErrorResponse: type: object properties: message: type: string description: A human-readable error message indicating what went wrong. example: Invalid request data issues: type: array items: type: object properties: code: type: string message: type: string path: type: array items: type: string required: - code - message - path additionalProperties: false description: Array of detailed validation error objects. example: - code: invalid_string message: Invalid UUID path: - id required: - message - issues additionalProperties: false title: ValidationErrorResponse description: Details about validation errors in incoming requests. securitySchemes: ApiKey: type: apiKey in: header name: x-api-key description: Your unique Avido API key ApplicationId: type: apiKey in: header name: x-application-id description: Your unique Avido Application ID ````