Authentication

API keys

Every request to the Typeless API must include an API key. Keys use the format:

tls_sk_<32 alphanumeric characters>

For example: tls_sk_AbC123... Create and manage your keys in the Typeless Console.

HTTP requests

Pass your key in the Authorization header using the Token scheme.

curl -X POST https://api.typelessapi.com/v1/transcribe \
  -H "Authorization: Token $TYPELESS_API_KEY" \
  -F "audio=@meeting.wav" \
  -F "model=typeless-1.0-pro"

WebSocket connections

Pass your key as a token query parameter in the WebSocket URL.

wss://api.typelessapi.com/v1/transcribe/stream?token=tls_sk_...

Managing keys

From the Typeless Console you can create, rename, and revoke keys. The plaintext key value is shown only once — at creation time. If you lose a key, revoke it and create a new one.

Security

Protect your API keys like passwords.

Never embed keys in client-side code or public repositories
Store keys in environment variables or a secrets manager
If a key leaks, revoke it immediately in the console and create a new one

Authentication errors

Code	HTTP	When
`MISSING_API_KEY`	401	Header/query missing or malformed
`INVALID_API_KEY`	401	Key revoked or not found
`INSUFFICIENT_BALANCE`	402	Account balance is zero — top up in the console
`ACCOUNT_SUSPENDED`	403	Account deactivated — contact support

See the Errors reference for full error handling guidance.

Quickstart Pre-recorded audio

Get Started

Transcription

Models & Pricing

SDKs

API keys

HTTP requests

WebSocket connections

Managing keys

Security

Authentication errors

​API keys

​HTTP requests

​WebSocket connections

​Managing keys

​Security

​Authentication errors

API keys

HTTP requests

WebSocket connections

Managing keys

Security

Authentication errors