Authentication

Protect, send, rotate, and revoke Fast Transcriber bearer API keys.

Create a key in the dashboard

API key management belongs to the signed-in Fast Transcriber account experience. It is not exposed as a bearer-authenticated v1 endpoint.

Open developer dashboard

Name keys after the application, environment, or automation that uses them.
An account can keep up to 10 active keys.
The full secret is displayed only at creation.

Send the key as a bearer token

Authorization: Bearer ft_live_replace_me

The scheme is case-insensitive, but the secret must remain exact and cannot contain spaces or surrounding quotes.

Protect credentials

Keep keys server-side

Public browser code, mobile bundles, logs, prompts, and repositories are not secret stores.

Separate environments

Use distinct keys so one integration can be revoked without interrupting another.

Rotate and revoke

Create a replacement key, update the consuming service, verify traffic, and revoke the old key. Revocation takes effect immediately. Fast Transcriber stores a SHA-256 hash rather than the recoverable secret.

A lost key cannot be displayed again

Create a replacement and revoke the lost credential. Do not wait for the secret to be exposed.

Authentication errors

Status	Code	Meaning
401	`missing_api_key`	No bearer key was supplied.
401	`invalid_api_key`	The key is malformed, unknown, or revoked.