Bucket Key Missing

bucket-key-missing · 409

The bucket has no key to list or sign with, so the API couldn't reach its files.

Nothing holds the bucket: issuing it a new key after the account came back failed partway. Rotating its credentials issues a key and clears this.

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

Common causes

  • The account was suspended and then came back, and issuing the bucket a new key failed partway.

How to fix the call

  • Rotate the bucket's credentials with POST /v1/buckets/<id>/credentials/rotate, then retry.
  • A service connected to the bucket reads the new key from its next deploy, so redeploy it.

Example response

json
{
  "type": "bucket-key-missing",
  "title": "Bucket Key Missing",
  "detail": "Bucket '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' has no key; rotate its credentials to issue one",
  "code": "BUCKET_KEY_MISSING",
  "bucketId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/objects",
  "method": "GET",
  "instance": "GET /v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/objects",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/bucket-key-missing"
}