> ## Documentation Index > Fetch the complete documentation index at: /docs/llms.txt > Use this file to discover all available pages before exploring further. # Get trace thread > Get a trace thread. ## OpenAPI ````yaml get /v2/sessions/{session_id} openapi: 3.1.0 info: title: Toqan Router API version: '2.0' description: Toqan Router API documentation servers: - url: https://router.toqan.ai/eu description: Frankfurt (Europe) - url: https://router.toqan.ai/br description: São Paulo (Brazil) security: - ApiKey: [] tags: - description: >- API keys authenticate programmatic access to the workspace. They expose opaque tokens, per-domain access grants, and budget and rate-limit constraints. name: API keys - 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: 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. - name: Traces description: >- Query and inspect ingested trace data: search trace summaries, aggregate metrics, and read individual traces and their spans. - name: Views description: Saved filters and columns for workspace observability pages. - description: List models available through the AI Router. name: Models - name: Alerts description: >- Alerts evaluate a telemetry 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: 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: 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 Toqan Router model catalog: every model Toqan Router 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: Monitors description: >- Monitors are custom observability dashboards for traces, runtime metrics, and logs. Each monitor holds widgets that chart one telemetry query. List the metrics, operations, and dimensions available to your workspace with `GET /v3/telemetry/capabilities`, or start from a preset with `GET /v2/monitors/presets`. - name: Notifiers description: Notifier destinations used to send delivery and workflow notifications. - 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: 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: Responses - name: Embeddings - description: Beta. Run typed classification questions against a classify model. name: Classify - description: Beta. Run classification decisions with the classify contract. name: Decisions - description: >- Run large offline workloads as JSONL batches and download OpenAI-compatible result files. name: Batches paths: /v2/sessions/{session_id}: get: tags: - Threads summary: Get trace thread description: Get a trace thread. operationId: GetSession parameters: - name: session_id in: path required: true schema: type: string responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/Thread' '401': description: >- Authentication required. See https://router.toqan.ai/docs/reference/errors for the error codes. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: >- The resource does not exist. See https://router.toqan.ai/docs/reference/errors for the error codes. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - ApiKey: [] x-code-samples: - lang: curl label: Core - Retrieve session source: | curl --request GET \ --url 'https://router.toqan.ai/eu/v2/sessions/thread_01HZXW2K7Y8Q9M0N1P2R3S4T5V' \ --header "Authorization: Bearer $TOQAN_API_KEY" components: schemas: Thread: required: - _id - external_id - duration - contact_ids - billing - usage - traces_count - tags type: object properties: _id: type: string description: Internal thread record ID. external_id: type: string description: Client-provided thread identifier used to group related traces. duration: type: number description: Total thread duration in milliseconds. format: double contact_ids: type: array items: type: string description: Contact IDs associated with the thread. billing: $ref: '#/components/schemas/ThreadBilling' usage: $ref: '#/components/schemas/ThreadUsage' traces_count: type: integer description: Number of traces associated with the thread. format: int32 tags: type: array items: type: string description: Tags used to categorize the thread. project_id: type: string started_at: type: string format: date-time updated_at: type: string format: date-time title: type: string description: >- Display title. Does not replace external_id and is not used to group traces. client: type: string description: >- Originating coding assistant or client, such as claude-code, cursor, or codex. repo: type: string description: >- Canonical git repository for a coding-agent thread, such as github.com/org/repo. kind: $ref: '#/components/schemas/ThreadKind' description: Whether this thread is a conversation or a coding-agent chat. ErrorResponse: type: object properties: message: type: string description: Human-readable error message. code: type: integer description: Numeric error code, when one is available. details: type: array items: {} description: Additional error details, when the service reports any. required: - message ThreadBilling: required: - input_cost - output_cost - total_cost type: object properties: input_cost: type: number format: double output_cost: type: number format: double total_cost: type: number format: double ThreadUsage: required: - prompt_tokens - completion_tokens - total_tokens type: object properties: prompt_tokens: type: integer format: int32 completion_tokens: type: integer format: int32 total_tokens: type: integer format: int32 ThreadKind: type: string enum: - THREAD_KIND_CONVERSATION - THREAD_KIND_CODING_AGENT securitySchemes: ApiKey: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.