Create a sandbox
Provisions a sandbox synchronously. The request blocks until the sandbox is ready (~2–3s typical). Returns 201 with status: "ready". Use a client timeout of at least 90 seconds. On provisioning failure the API returns 503.
GET /sandboxes/{id}/wait remains for reconnect edge cases (e.g. after resume); it is not required after create.
Network egress
Control outbound network access at create time with the egress object, or the legacy blockOutbound: true shorthand (maps to deny_all). You cannot set both on the same request.
| egress.mode | Behavior |
|---|---|
| open | Full outbound internet (default when omitted) |
| deny_all | All outbound connections blocked |
| restricted | Default deny + allowlist in egress.allow |
Change policy later with PUT /sandboxes/{id}/egress.
Request body
Example request
{
"egress": {
"mode": "restricted",
"allow": [
"1.1.1.1",
"api.example.com"
]
}
}Response
Sandbox provisioned and ready
Example response
{
"message": "Sandbox created"
}Changes
Changed in 3 of the 5 revisions of this API.14
- ▲
removed the success response with the status
200response-success-status-removed
- ○
added the non-success response with the status
503response-non-success-status-added
- ○
added the success response with the status
201response-success-status-added
- ▲
- ○
added the new optional request property
egressnew-optional-request-property
- ○
- ○
the request property
regionbecame optionalrequest-property-became-optional
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○