curl or any other HTTP client. The AI Object Storage API allows users to set organization-wide access policies, configure bucket settings, and manage access keys.
- The API server is
https://api.coreweave.com. - Replace
[API-ACCESS-TOKEN]in the following examples with your CoreWeave API access token.
Operations
For per-endpoint request and response schemas, see the CWObject pages in the left sidebar under AI Object Storage API. Each HTTP endpoint maps to a gRPC method on the
CWObject service:
Authentication
Most requests authenticate with a CoreWeave API access token sent as a bearer token in theAuthorization header (the TokenAuth scheme). For required permissions on each operation, see IAM Access Policies.
Three endpoints are special and call out their own authentication requirements on the per-operation page:
POST /v1/cwobject/temporary-credentials/samlandPOST /v1/cwobject/temporary-credentials/oidcare anonymous on the CoreWeave side. They exchange an external IdP assertion for a CoreWeave access key, so no CoreWeave bearer token is required.GET /v1/cwobject/temporary-credentials/oidc/{orgId}uses theContainerCredentialsAuthscheme: send a raw JWT/OIDC token as theAuthorizationheader value with noBearerprefix. This shape matches the AWS container-credentials provider for in-cluster workloads.
gRPC schema and SDKs (Buf)
The AI Object Storage API is also exposed as a gRPC service defined in Protobuf. Use the same API host,https://api.coreweave.com, with token-based authentication.
- Service:
CWObject(packagecoreweave.cwobject.v1) - Public BSR module:
buf.build/coreweave/cwobject - TypeScript SDK namespace:
@buf/coreweave_cwobject.bufbuild_es
Access-key status values
Thestatus field on access keys uses the proto-3 enum AccessKeyStatus. The wire format is the symbolic name:
Access policies
Access policies use a small grammar that maps cleanly to the AWS IAM shape. Policies are documented in IAM Access Policies; the canonical list of actions (cwobject:*, s3:*) lives in the CoreWeave AI Object Storage actions reference.
Two fields on the policy schema are open strings on the wire today (upstream emits them as type: string with no enum: list):
The auto-generated reference documents these values in the field description prose; the overlay does not add a tooling-enforced
enum constraint, because upstream would have to renegotiate that constraint every time it adds a new effect or policy version. See the storage overlay report for the upstream recommendation.
Pagination
Thelimit parameter on ListAccessKeyInfo and ListBucketInfo accepts values from 1 to 1000 (declared in the proto, reasserted in the overlay because protoc-gen-openapi strips the bound). Use offset for zero-based pagination.