---
seo:
  description: >-
    Canonical V0 public API for AVTR. Six endpoints only — legacy/bridge routes
    (/start, /status, /ws-token, DELETE /v1/sessions/{id}, /sfu/*,
    catalog/system…
sidebar:
  label: Overview
title: AVTR Public API v1
---
Canonical V0 public API for AVTR. Six endpoints only — legacy/bridge routes (`/start`, `/status`, `/ws-token`, `DELETE /v1/sessions/{id}`, `/sfu/*`, catalog/system routes) are deliberately absent from this spec even though the deployed Worker still serves them.

All `/v1/*` routes require an API key (Bearer or `x-api-key`). Responses use the flat AVTR error taxonomy body (`{code, message, request_id, doc_url, retry_after?}`) for every 4xx/5xx.

Provider credentials are per-session ephemeral and held in Gateway process memory ONLY for the session lifetime; never persisted. `provider_connection_id` is rejected at the schema level. Managed provider connections are deferred to a post-V0 optional mode.

<ApiOverview source="reference" />

## API Keys

API key management endpoints.

<ApiTagOperations source="reference" tag="api-keys" />

## Sessions

Session lifecycle endpoints.

<ApiTagOperations source="reference" tag="sessions" />