AssemblyAI Identity and Endpoint Setup

Overview

Configure AssemblyAI keys, regional endpoints, and server-versus-browser authentication safely. Treat live audio, transcript content, credentials, spend, and destructive state as separately governed boundaries.

Prerequisites

• The target repository or integration path and the requested operator outcome.
• The AssemblyAI project, environment, region, data classification, and accountable owner.
• Current first-party documentation plus credentials only for a narrowly approved live check.

Current Contract

Pre-recorded REST uses the approved US or EU api.assemblyai.com host and the raw project key in the Authorization header. Streaming uses the v3 WebSocket host. Browser and mobile clients receive short-lived, single-use streaming tokens from a trusted backend; they never receive the project key.

Authentication

For live work, inject ASSEMBLYAI_API_KEY from an approved secret manager and send the raw value only in the AssemblyAI Authorization header to the configured first-party host. Never print, commit, place in a URL, or expose it to an untrusted client. Callback secrets and temporary streaming tokens are separate credentials.