Mint a realtime ephemeral client secret

Calls the upstream realtime provider’s client_secrets endpoint to mint a short-lived ephemeral token (e.g. for browser-based WebRTC clients). Bifrost selects a provider key, evaluates governance, and proxies the response. The returned token is cached and mapped to the originating virtual key for downstream attribution.

Request body must be JSON. session.model (or top-level model) must use provider/model form.

POST /v1/realtime/client_secrets

Error

A valid request URL is required to generate request examples

200

{}

Authorizations

BearerAuthBasicAuthVirtualKeyAuthApiKeyAuth

Authorization · string · header · required

Bearer token authentication. Use your provider API key or Bifrost authentication token. Virtual keys (prefixed with sk-bf-) can also be passed here.

Body

application/json

Provider-specific realtime client-secret payload (passthrough).

Response

200

application/json

Upstream client-secret response (provider passthrough)

Provider-specific response body