Bucket Not Ready

bucket-not-ready · 409

The bucket isn't ready, so the API has no key to hand out and no files to show.

The bucket's state shows in detail only: the API writes the HTTP status into status over it. Read the bucket for its state.

Besides the members every error carries, this type adds code and bucketId.

Common causes

  • The bucket was created moments ago and is still pending or provisioning.
  • Creating the bucket failed, so it is failed.
  • Its credentials were asked for, or rotated, before it was ready.

How to fix the call

  • Read the bucket with GET /v1/buckets/<id> and wait while its status is pending or provisioning, then retry.
  • If its status is failed, tell the user, quoting detail.

Example response

json
{
  "type": "bucket-not-ready",
  "title": "Bucket Not Ready",
  "detail": "Bucket '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' has no credentials while it is provisioning",
  "code": "BUCKET_NOT_READY",
  "bucketId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "status": 409,
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/credentials",
  "method": "GET",
  "instance": "GET /v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/credentials",
  "docs": "https://ghaym.me/docs/errors/bucket-not-ready"
}