Realtime
Recorded
Concepts
Guides
API Reference
Authentication model
- All API requests require an API key. Keys are prefixed
sk-; the server stores only a SHA-256 hash of the key. - Browser clients must never embed the long-lived key. Instead, your backend exchanges it for a short-lived session token (
rt_…, valid 60 s, HMAC-SHA256 signed) — see Authentication.
Key handling best practices
- Store keys in a secret manager or server-side environment variables.
- Never put
sk-…in URLs, client code, or logs. - Rotate and revoke keys on a schedule and on team changes.
- Use separate keys per environment.
Data handling
- Realtime audio is streamed through the gateway to the recognition upstream; it is not written to durable storage.
- Recorded (segment / batch) transcription fetches audio from the
audio_urlyou provide and produces transcripts. Intermediate workflow state is checkpointed in object storage so long jobs can resume (see Batch Jobs). - Operational logs are structured and do not contain plaintext audio or API keys.
- Transcripts are ultimately yours to persist; see Data Retention for what the service keeps.
Reporting a concern
- Contact
support@lansonai.comfor security questions or data-deletion requests.