FAQ
Common troubleshooting guidance and answers for integrating with the Soniox API.
This page answers common questions related to integrating with the Soniox API.
High WebSocket connection startup time is usually caused by one or more of the following:
- Network latency: High round-trip time between your client and Soniox increases the duration of the TLS handshake and WebSocket upgrade.
- Region selection: Using an endpoint located far from your compute environment adds unnecessary cross-region latency during connection establishment. See Data residency for more info.
- Large initial context payload: Sending a large context during initialization delays readiness because the server must fully receive and process the payload before the session becomes active.
To minimize perceived startup delay, you should always buffer audio locally before the WebSocket connection is established and immediately stream all buffered audio chunks after sending the initial configuration message.
You can request a limit increase from the Soniox Console organization limits page. Requests are reviewed within 1-3 business days.
Yes. Soniox provides standard legal and compliance documentation for companies integrating the Soniox API into their products or services. This may include an MSA, DPA, and security or compliance documentation required for procurement or security review processes.
Documentation is available for Business and Enterprise customers. Please contact sales@soniox.com to request access or begin the review process.