Skip to main content
Use these endpoints when you need speech input, speech output, or transactional email from the gateway.

WebSocket /v1/listen

Use this endpoint for live streaming speech-to-text. Auth: required (Authorization: Bearer bos_live_sk_...) Proxy to Deepgram’s live streaming STT. Connect to the gateway with your Basics API key; the gateway handles the upstream connection and keeps provider credentials server-side. URL: wss://api.basicsos.com/v1/listen?model=nova-2&diarize=true&... Use the same query params as Deepgram’s Listen API.
  • Client → gateway: send binary audio frames
  • Gateway → client: receive Deepgram JSON transcript results
  • When either side closes the connection, the other is closed as well

POST /v1/audio/transcriptions

Convert speech to text. Auth: required This endpoint supports two input modes, so you can work with browser uploads or direct JSON payloads.

Multipart form-data

Recommended for browser uploads.

JSON with base64 audio

JSON fields

Response

Returns provider-specific transcription JSON from Deepgram.

POST /v1/audio/speech

Convert text to speech. Auth: required

Request body

Response

Returns a binary audio body. Common response headers:
  • Content-Type: provider audio type such as audio/mpeg
  • x-request-id: internal request ID

POST /v1/email/send

Send a simple tenant-scoped text email through Basics. Auth: required. BYOK is not supported.

Request body

Request fields

Success response

Common errors

  • 503 with code: "service_unavailable" when email is not configured
  • 422 with code: "invalid_payload" for validation errors
  • 4xx or 5xx with code: "email_send_failed" if the Resend call fails