> ## Documentation Index > Fetch the complete documentation index at: https://docs.omnia-voice.com/llms.txt > Use this file to discover all available pages before exploring further. # List logged exchanges > Your workspace's captured chat exchanges, newest first. Nothing is stored until a workspace owner enables request logging — it is **off by default**. Only successful chat completions on the shared catalog are captured; content is secret-scrubbed at capture and deleted automatically at the end of your retention window. ## OpenAPI ````yaml /openapi.json get /v1/logs openapi: 3.1.0 info: title: Omnia Management API description: >- The management API behind the improvement loop: capture and setup, request logs and datasets, grades (labels), judges (criteria), evals and deploy gates, fine-tuning and reinforcement learning, dedicated GPU endpoints, and model aliases and versions. Authenticated with a workspace API key (sk_sovereign_...). The inference API (chat, embeddings, rerank, responses) is OpenAI-compatible and documented separately. Responses are snake_case, list endpoints on the loop products use the {"object": "list", "data": [...]} envelope, and refusals use the same nested error shape the gateway emits: {"error": {"message", "type", "code"}}. Request bodies on the loop products (logs, labels, criteria, evals, datasets, aliases) are snake_case; the training and infrastructure products (fine-tuning, GRPO, environment tools, dedicated, model-version adoption) validate camelCase bodies, and each schema below says which it is. Endpoints that spend money require a key minted by a workspace owner or admin and return 403 otherwise. version: 1.0.0 servers: - url: https://gateway.omnia-voice.com description: Production - url: https://platform.omnia-voice.com/api description: Production (legacy alias — same API, older base URL) security: - bearerAuth: [] paths: /v1/logs: get: tags: - Logs summary: List logged exchanges description: >- Your workspace's captured chat exchanges, newest first. Nothing is stored until a workspace owner enables request logging — it is **off by default**. Only successful chat completions on the shared catalog are captured; content is secret-scrubbed at capture and deleted automatically at the end of your retention window. operationId: listLogs parameters: - name: model in: query schema: type: string description: Only exchanges served by this model. - name: tag in: query schema: type: string description: Only exchanges whose request carried this X-Omnia-Tag. - name: segment in: query schema: type: string description: >- Only exchanges in this auto-detected traffic segment (a `segment` value from a logs row — the family of system prompts sharing one template). Composes with tag: segments are detected, tags are declared. - name: finish_reason in: query schema: type: string enum: - stop - length - tool_calls - name: cache_hit in: query schema: type: boolean description: true = cache replays only; false = exclude them. - name: start in: query schema: type: integer description: Unix seconds, inclusive. - name: end in: query schema: type: integer description: Unix seconds, exclusive. - name: limit in: query schema: type: integer minimum: 1 maximum: 100 default: 25 - name: offset in: query schema: type: integer minimum: 0 default: 0 responses: '200': description: A page of logged exchanges. content: application/json: schema: type: object properties: object: type: string example: list total: type: integer limit: type: integer offset: type: integer data: type: array items: $ref: '#/components/schemas/LogEntry' '401': $ref: '#/components/responses/Unauthorized' '409': description: >- Request logging is disabled for this workspace, so nothing is captured. Enable it in workspace settings. content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: LogEntry: type: object properties: request_id: type: string created_at: type: integer description: Unix seconds. model: type: string tag: type: string description: From the X-Omnia-Tag request header. segment: type: string description: >- Auto-detected traffic segment: the family of system prompts sharing one template, stable under interpolated dates/ids/context. Detected retroactively from logged traffic — zero setup. Pass it back as ?segment= to slice, or into eval sample_filters.segment. segment_exact: type: string description: >- The exact system-prompt hash within the family — precision when one interpolated variant matters. trace_id: type: string finish_reason: type: string streamed: type: boolean cache_hit: type: boolean fallback_from: type: string description: Set when a fallback model served the request. prompt_tokens: type: integer completion_tokens: type: integer messages: type: array items: type: object description: The request messages, secret-scrubbed at capture. response: type: object description: >- The assistant message (including tool_calls), secret-scrubbed at capture. Error: type: object properties: error: type: object properties: message: type: string type: type: string description: >- invalid_request_error, insufficient_quota, rate_limit_error, or api_error. code: type: string description: >- Machine-stable cause, e.g. invalid_api_key, not_found, insufficient_permissions, precondition_failed. required: - message - type - code description: >- Every refusal — gateway and management API alike — uses this one envelope. responses: Unauthorized: description: Missing, malformed, or revoked API key. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Invalid API key type: invalid_request_error code: invalid_api_key securitySchemes: bearerAuth: type: http scheme: bearer description: >- Your workspace API key, e.g. `sk_sovereign_...`, sent as `Authorization: Bearer `. ````