buf.build/coreweave/sandbox. Use them when you integrate from a language that has no first-party CoreWeave client. You can also use them for a remote procedure call (RPC) that the Python client or the TypeScript client (@coreweave/cwsandbox) doesn’t expose.
The module page lists the service and field definitions. 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.
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 logical-runner endpoint for direct connections with sandbox-scoped credentials:
NetworkService isn’t available yet: every RPC returns UNIMPLEMENTED with reason CWSANDBOX_NOT_IMPLEMENTED. More generally, RPC availability depends on the organization, deployment, and placement mode. Other unimplemented RPCs can return UNIMPLEMENTED without that structured reason. Inspect the RPC code and any error details.
PlacementOrgConfigService remains registered on api.coreweave.com for legacy cleanup. Its configuration is no longer enforced: UpdatePlacementOrgConfig returns UNIMPLEMENTED, while Get and Delete remain available to inspect and remove legacy rows. These calls require sandbox_admin and target the caller’s own placement organization. This service is excluded from the supported REST reference.
NetworkConfigService manages dynamic network configurations. Its availability prerequisites include API enablement and runner support for live updates.
Requests to api.cwsandbox.com and api.coreweave.com authenticate with a CoreWeave API access token. For how to create one and grant the sandbox_user or sandbox_admin identity and access management (IAM) action, see Authentication.
The direct logical-runner data-plane endpoint uses mutual Transport Layer Security (TLS) with the sandbox-scoped client certificate and trust bundle returned by ConnectSandbox. It doesn’t use the API bearer token.
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
Generate code locally
To generate code locally, follow these steps:-
Configure a
buf.gen.yamlfile with the plugins to run and their output directories. -
From the directory containing that file, run:
Read failed Compose build logs
For a failed service build from Create a sandbox from a Compose file, callSandboxService.GetSandboxBuildLogs() over Connect. Replace API_ACCESS_TOKEN, SANDBOX_ID_VALUE, and SERVICE_NAME with your API access token, sandbox ID, and Compose service name:
Get a failed build log link
url and its expireTime. Download from that URL without sending your API access token. The REST binding returns 302 Found with the URL in the Location header and no response body.
See also
For related guidance, see the following pages:- 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.
- Sandboxes Python client: the higher-level
cwsandboxclient built on this API. - Direct sandbox connections: how a client reaches
SandboxDataPlaneServiceover mutual TLS.