Bucket Upload Invalid

bucket-upload-invalid · 400

The upload names a key or a part the batch can't take, so the API signed nothing.

These come from the upload routes the console's file browser calls; an app writing with its own S3 keys talks to the store and never meets them. reason says which: outside-prefix, folder-key or part-out-of-range. Each is a fault in the calling code, not a state the bucket is in.

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

Common causes

  • outside-prefix: the key isn't under the folder the batch was opened for.
  • folder-key: the key ends in /, which names a folder, not a file.
  • part-out-of-range: a part number is past the file's last part, by the size given when the file was signed.

How to fix the call

  • Upload a key under the batch's folder, or open a batch for the folder the key is in.
  • Drop folder keys: a folder exists while it holds files.
  • Work out the part count from the file's size, in parts of 16 MiB.

Example response

json
{
  "type": "bucket-upload-invalid",
  "title": "Bucket Upload Invalid",
  "detail": "Cannot upload 'images/logo.png': outside-prefix",
  "code": "BUCKET_UPLOAD_INVALID",
  "key": "images/logo.png",
  "reason": "outside-prefix",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/upload-batches/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/uploads",
  "method": "POST",
  "instance": "POST /v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/upload-batches/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/uploads",
  "status": 400,
  "docs": "https://ghaym.me/docs/errors/bucket-upload-invalid"
}