Update Sandbox
Update proxy-visible sandbox settings such as public exposed ports and whether ingress can skip authentication checks.
exposed_ports and allow_unauthenticated_access), the sandbox name, and the egress network policy. The network field is tri-state: omit it to leave the policy unchanged, send an object to replace it, or send null to clear it. See Networking for details.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The ID of the sandbox.
Body
Set or clear unauthenticated ingress routing for this sandbox.
Replace the exposed port allowlist. Pass an empty array to clear it and revert to the default management port only.
1 <= x <= 65535Update the egress network policy of the running sandbox. This field is tri-state: omit it to leave the current policy unchanged, send an object to replace the whole policy, or send an explicit null to clear it (unrestricted egress). The change is applied to the live sandbox firewall as one atomic swap with no enforcement gap; already-established connections are not revoked. If a hostname in the new policy fails to resolve, the update is rejected and the previous policy stays enforced.
Response
Sandbox updated successfully
pending, running, snapshotting, suspending, suspended, terminated Milliseconds since Unix epoch.
Whether sandbox ingress may route requests without auth validation.
Present when status is pending.
Platform-specific termination outcome string returned for completed sandboxes.
Canonical server-provided base for sandbox-specific ingress.
Sandbox-specific management URL derived from ingress_endpoint.
Additional routable ingress ports. When null, only the management port 9501 is routable.
1 <= x <= 65535