Hanzo
OpenapiS3

Create a bucket in your org

Creates a new bucket in the caller's own namespace and answers 201 with its friendly name and creation time.

POST /v1/s3/buckets

Addresshttps://api.hanzo.ai/v1/s3/buckets
MethodPOST
Operationpost_s3_buckets
AuthAuthorization: Bearer $HANZO_API_KEY

Creates a new bucket in the caller's own namespace and answers 201 with its friendly name and creation time.

The name is validated exactly as sent and never quietly normalised: it must match ^[a-z0-9]([a-z0-9-]{0,38}[a-z0-9])?$, so a mixed-case name is a clean 400 rather than a bucket created as photos that the caller keeps asking for as Photos. A name already in use in the caller's own namespace is 409.

A validated principal is required, and every bucket and key is resolved inside the caller's own org: physical bucket names are derived from the org, so a tenant cannot name another's storage. The operation is billed per call — the balance is checked BEFORE anything is touched, so an unfunded org is refused with nothing done, and the debit happens only after the work succeeds. Object storage that is not configured answers 503 under this subsystem's own name rather than falling through to another.

Request

The document declares no body for POST /v1/s3/buckets. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_s3_buckets, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo s3 buckets create

S3 API · All Hanzo APIs · Interactive reference

How is this guide?

On this page