Connect sandbox
Issue short-lived client credentials and return the direct data-plane endpoint of a running sandbox.
cwsandbox Python SDK implements for you.Authorizations
CoreWeave API access token sent as a bearer token.
Path Parameters
Body
ConnectSandboxRequest requests sandbox-scoped direct-connection credentials. The sandbox must be running and its Runner must advertise a compatible direct data-plane endpoint.
DER-encoded PKCS #10 certificate signing request. The issuer validates the proof-of-possession signature and copies only the public key; requested identity, extensions, and lifetime are ignored.
Operations to authorize on the issued certificate. At least one concrete permission is required. SANDBOX_DATA_PERMISSION_UNSPECIFIED and unknown values are invalid. The server returns only permissions allowed for the caller.
SANDBOX_DATA_PERMISSION_UNSPECIFIED, SANDBOX_DATA_PERMISSION_EXEC, SANDBOX_DATA_PERMISSION_STREAM_EXEC, SANDBOX_DATA_PERMISSION_STREAM_LOGS, SANDBOX_DATA_PERMISSION_WRITE_FILE, SANDBOX_DATA_PERMISSION_READ_FILE Response
OK
SandboxConnection contains everything except the client private key needed to establish a sandbox-scoped direct connection.
Stable absolute URI for the logical Runner data-plane endpoint.
PEM certificate chain for the public key in the request CSR. The leaf certificate is first.
PEM trust bundle for authenticating the endpoint. Empty means the endpoint chains to roots available from the client's system trust store.
Time at which the client certificate and established connection expire.
Opaque stable identity of the logical Runner endpoint.
Transport for the issued connection. Successful responses use SANDBOX_DATA_TRANSPORT_DIRECT_MTLS. SANDBOX_DATA_TRANSPORT_UNSPECIFIED means no transport is specified and is not emitted for a successful connection.
SANDBOX_DATA_TRANSPORT_UNSPECIFIED, SANDBOX_DATA_TRANSPORT_DIRECT_MTLS Protocol for the issued connection. Successful responses use SANDBOX_DATA_PROTOCOL_CONNECT_H2_V1. SANDBOX_DATA_PROTOCOL_UNSPECIFIED means no protocol is specified and is not emitted for a successful connection.
SANDBOX_DATA_PROTOCOL_UNSPECIFIED, SANDBOX_DATA_PROTOCOL_CONNECT_H2_V1 Effective permissions encoded in the issued certificate. Successful responses contain at least one permission from the intersection of requested and allowed permissions and do not contain SANDBOX_DATA_PERMISSION_UNSPECIFIED.
SANDBOX_DATA_PERMISSION_UNSPECIFIED, SANDBOX_DATA_PERMISSION_EXEC, SANDBOX_DATA_PERMISSION_STREAM_EXEC, SANDBOX_DATA_PERMISSION_STREAM_LOGS, SANDBOX_DATA_PERMISSION_WRITE_FILE, SANDBOX_DATA_PERMISSION_READ_FILE