buf.build/coreweave/sandbox. Use them when you integrate from a language that has no first-party CoreWeave client, or when you need an RPC that the Python client or the TypeScript client (@coreweave/cwsandbox) doesn’t expose.
The module page is the reference for the API itself: every service and field, the JSON encoding rules, and the error contract. Use coreweave.sandbox.v1 for new integrations. The earlier coreweave.sandbox.v1beta2 package is still served for existing clients, and also carries profile templates and runner enrollment.
CoreWeave Serverless sandboxes are in public preview.
Endpoints
Every RPC is served over the Connect protocol, and the same endpoints accept gRPC and gRPC-Web clients. Thev1 services are split across two hosts, plus a per-sandbox endpoint for direct connections:
NetworkService isn’t available yet: every RPC returns UNIMPLEMENTED. More generally, not every RPC is enabled for every organization or placement mode. A call that isn’t available returns UNIMPLEMENTED with reason CWSANDBOX_NOT_IMPLEMENTED.
Requests authenticate with a CoreWeave API access token. For how to create one and grant the SANDBOX_USER or SANDBOX_ADMIN IAM action, see Authentication.
Install a generated SDK
The Buf Schema Registry builds SDKs for the module on demand. The following commands install common language and plugin combinations:Install a generated SDK
buf generate at the module: buf generate buf.build/coreweave/sandbox.
See also
- Sandboxes architecture: how the gateway brokers runtime requests, and the control plane and data plane split.
- API overview: authentication, pagination, field masks, and error handling for the control plane.
- Sandbox Python client: the higher-level
cwsandboxclient built on this API. - Direct sandbox connections: how a client reaches
SandboxDataPlaneServiceover mutual TLS.