Guides
Practical Soniox guides for streaming architectures, temporary API keys, usage logs, and concurrency limits.
Soniox guides help you design production-ready Speech-to-Text and Text-to-Speech integrations around real-time streaming, secure client access, usage attribution, and operational limits.
Use these guides when you need architectural guidance beyond the API reference: how to connect browsers to Soniox, when to introduce a proxy, how to issue short-lived credentials, and how to monitor usage and capacity.
Stream directly from a browser microphone to Soniox WebSocket APIs with temporary API keys for the lowest possible latency.
Route client audio through your server before forwarding it to Soniox when you need server-side inspection, transformation, or storage.
Create short-lived, restricted credentials so untrusted clients can connect directly without exposing long-lived API keys.
Send your API key with the WebSocket connection, in the Authorization header or the protocols list, plus connection timeouts and the connection limit.
Move from api_key in the start message to sending the key with the connection, with before and after code.
Limit each API key to the parts of the API it needs, with read and write levels, and resolve permission_denied errors.
Read balance, usage, limits and projects across your organization, and create or delete project API keys from your own tooling.
Inspect per-request usage records for model, duration, tokens, cost, request IDs, and client_reference_id attribution.
Understand real-time concurrency caps, active stream counts, project and organization limits, and 429 limit responses.