Create WebRTC connection
Create a new WebRTC connection. See WebRTC Connections.
Authorizations
API key authorization. Pass your API key in the Authorization header as a Bearer token. Both new (gsk_*) and legacy (gsk-) API keys are accepted, e.g. Authorization: Bearer gsk_... or Authorization: Bearer gsk-....
Body
"prod_123"
"Support agent (WebRTC)"
Pipecat Cloud PUBLIC API key (pk_...) Galtea uses to provision a room via the runtime /start call. This is NOT the pcc_pat_ Personal Access Token used to deploy agents. Encrypted at rest and never returned; read hasApiKey to know whether one is set. On update, omit it to keep the stored key.
"pk_..."
Name of your deployed Pipecat Cloud agent. Must match that agent's deployed name exactly. Galtea passes it to the Pipecat Cloud /start call to launch the session; if no deployed agent has this name, /start fails.
"my-voice-agent"
"webRtcConnection_123"
"user_123"
Whether the voice agent opens the conversation once the session connects. false (default) means the simulated caller speaks first; true suits interviewer-style agents that greet first.
false
Response
WebRTC connection created successfully
"prod_123"
"Support agent (WebRTC)"
Name of your deployed Pipecat Cloud agent. Must match that agent's deployed name exactly. Galtea passes it to the Pipecat Cloud /start call to launch the session; if no deployed agent has this name, /start fails.
"my-voice-agent"
"webRtcConnection_123"
"user_123"
Whether a Pipecat Cloud API key is stored for this connection.
true
Whether the voice agent opens the conversation once the session connects. false (default) means the simulated caller speaks first; true suits interviewer-style agents that greet first.
false