GET
Get ICE Servers

Overview

Returns the ICE server configuration (STUN and TURN) a WebRTC client needs to establish voice/video calls. The shape matches the browser’s RTCConfiguration.iceServers, so you can pass it straight into an RTCPeerConnection. The SDK calls this for you when you set appId + apiUrl on the client — you usually don’t need to call it directly. See Voice & Video Calls (SDK).
Auth: any valid caller for the app — a dashboard JWT, an SDK token (Authorization: Bearer …), or X-Api-Key + X-Api-Secret.

Path Parameters

string
required
App ID (UUID).

Example Request

Response

array
Array of ICE server entries ({ urls, username?, credential? }).

Success (200)

Using it directly

If no turn: entry is returned, calls will fail for participants behind strict NATs. Make sure a TURN server is configured for your app.

How calls work

Signaling, ICE/TURN, and the call lifecycle.