Skip to main content
The Realtime API exposes OpenAI-compatible low-latency text and audio conversations through websocket sessions plus an HTTP endpoint for short-lived client tokens.

WebSocket Connection

Open a realtime websocket session directly when your backend can securely hold the DGrid API key.

Query Parameters

Client Events

Server Events

Create Realtime Session Token

Use the realtime endpoint example shown below when you need an authenticated GET request against the realtime HTTP entrypoint.

Request Headers

Response Body

WebSocket Events

Plan your client around a small set of request and response event types for low-latency conversational streaming.

Core Client Events

Core Server Events

Integration Guidance

  1. Buffer client-side audio in small chunks and use input_audio_buffer.commit to signal turn boundaries.
  2. Listen for both response.text.delta and response.audio.delta if the session supports multimodal output.
  3. Use the HTTP session token endpoint for browser clients so the long-lived API key never reaches the client.