On our github you can find a sample application that illustrates how to do live microphone capture from a web browser and receive real-time transcription results.

https://github.com/voicegain/platform/tree/master/examples/microphone-websocket

Below is the content of the README.md from that example:

Microphone capture sample code

What this code demonstrates:

• microphone capture in a browser
• sending captured audio over one websocket
• receiving transcribed audio over another websocket

The files included in this example are:

• audio-services.js - a service that captures the microphone audio and a service that sends the captured audio via websocket to Voicegain
• config.js - has the JWT token
• index.html - simple web page with Start/Stop buttons and a place for recognition output
• microphone-capture.js
  • function that initiates connection to https://api.voicegain.ai/v1/asr/transcribe/async Web API - the response will contain the send websocket url (for audio) and the receive websocket url (for transcription results)

See comments throughout the code for details.

Before you run the demo:

• Disable same-origin policy in chrome: https://www.thegeekstuff.com/2016/09/disable-same-origin-policy/
  This is needed because we will run the web client on localhost and will be making web api requests to api.voicegain.ai
  On Windows, the command may be:
  "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-web-security --user-data-dir="c:/someFolderName"
• Add a valid Voicegain JWT-token in config.js file for authorization

Running the demo:

• launch the index.html file

Notes regarding JWT and security

In this simple demo, the JWT token is accessible on client side plus we have issues with cross-origin.

In a real application, the request to https://api.voicegain.ai/v1/asr/transcribe/async would be wrapped in a server-side http method that would pass the JWT without exposing it to the web client.

The two websocket requests can be done directly from the web client because the websockets they reference have random one-time-use names. Also websockets can cross domain communication, and they are not limited by the SOP (Same Origin Policy).