BlyntBlynt API

Overview

Running your custom speech model via the Blynt API.

Blynt builds a speech recognition engine tuned for your product and runs it as a dedicated deployment. You reach that deployment with a deployment id and an API key, both provided by Blynt.

There are two APIs, and they are alternatives. Which one you use is fixed by your deployment: a deployment is provisioned either for real-time streaming or for synchronous transcription, and the deployment id you were given determines which of the two it answers on. It is not a per-request choice. If you need both, you need one deployment of each - talk to the Blynt team.

The two APIs

Real-time APISync API
TransportWebSocket (wss://)HTTP POST
Provisioned foraudio that arrives as the user speaksrecordings that are already complete
Resultsturn_partial while decoding, turn_ended at the endone JSON response
Unit of workone connection, many conversational turnsone request, one audio file
Languagesfr, en, pt, de, es, itfr, en, pt, de, es, it
Contextual biasingsession-level and per turnone context per request
Limitsthe lifetime of the connection48 MiB and 480 seconds per request
Framework pluginsPipecat, LiveKit—

Both take the same API key and the same contextual biasing shape, so what you learn on one side carries over to the other.

Calling the wrong API for a deployment fails. A deployment provisioned for Real-time answers 400 on POST /transcribe; a deployment provisioned for Synchronous transcription rejects the WebSocket connection. If you are unsure which one your deployment serves, ask the Blynt team.

Quickstarts

Learn more

On this page