Pre-initialize a call (agent configuration, variables initialization, and resources) before an inbound SIP call arrives, reducing cold-start latency to near zero.
Async: Returns the call_id immediately. Poll GET /v1/calls/{call_id} and wait for the status to become staged before triggering the SIP call.
Sync: Blocks until the call is ready (status staged) or a timeout occurs (HTTP 408).
Once staged, trigger the inbound SIP call with the header:
X-Rounded-Call-Id: {call_id}
This ensures the call is routed to the staged agent.
Call status flow: initiated → staged → ringing → in_progress → completed
If no SIP call arrives within the staging timeout (60s), the call is marked no_answer and cleaned up.
Tip: If your agent uses Call context: Variables initialization to load data when processing a call, prefer using this endpoint to prepare it beforehand.
The API Key created in Rounded Studio.
If true, block until the call is ready (status 'staged') or timeout.
Request body for staging an inbound SIP call.
This endpoint is only supported for inbound calls. Staging pre-initializes the call (agent configuration, variables, and resources) before the actual inbound SIP call arrives, reducing cold-start latency to near zero.
Once staged, the inbound SIP call must include the header
X-Rounded-Call-Id: <call_id> so it is routed to the staged call.
The caller's phone number in E.164 format.
"+33912345678"
The destination phone number in E.164 format.
"+33612345678"
The ID of the agent that will handle the call.
"411b82c8-462a-4e1b-89bc-10ab3ce1ed29"
Initial variable values to inject into the agent conversation before it starts.
Call staging initiated (async) or call staged and ready (sync)
Response from staging a SIP call.
The call_id is used to:
GET /v1/calls/{call_id} to check when the status becomes staged (call ready).X-Rounded-Call-Id SIP header value when triggering the inbound call.{
"details": [
{
"field": "email",
"message": "Invalid email format"
}
],
"message": "An error occurred while processing your request",
"status": 400,
"type": "generic_error"
}