Get ICE servers
Fetch STUN and TURN configuration with fresh ephemeral credentials for an RTCPeerConnection.
GET
Get ICE servers
Use this endpoint to fetch the ICE server configuration that your client should pass to
Example response when TURN is configured:
When TURN is not configured on the gateway, the response contains only STUN entries.
RTCPeerConnection before creating an offer. Each response returns the STUN servers configured on the gateway and, when TURN is enabled, a TURN entry with fresh HMAC-SHA1 credentials that expire 24 hours after issue.
When to use it
Call this endpoint instead of hardcoding ICE servers in your client when:- You expect users on networks that block UDP (for example, corporate firewalls). The response includes a
turns:URL on port 443 so media can relay over TLS. - You want short-lived credentials issued per session instead of long-lived shared secrets in your client code.
Authentication
Pass a Studio JWT or connector token using either:- The
tokenquery parameter —?token=<jwt> - The
Authorizationheader —Authorization: Bearer <jwt>
401 Unauthorized.
Example
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Studio JWT or connector token. Alternative to the Authorization header.
Response
ICE server configuration
List of STUN and TURN servers for the client to use.
Last modified on May 27, 2026
Get ICE servers

