Skip to main content
string
required
The API key for your account. You can find this in your account settings.
Chunked Complete assembles the parts sent with Chunked Part into the final file. The part list is read on the server, so you only send the upload token. Once it answers, the file is stored and counts against your quota. Requires the blob:write scope, or the upload token that opened the upload, and an active plan. What happens on a refusal depends on the cause:
  • The upload is kept open when the account has no active plan (PERMISSION_DENIED), is over its quota (STORAGE_QUOTA_EXCEEDED) or storage is unavailable (503). Fix the cause and call Complete again, without re-sending any part.
  • The upload is aborted and its parts are discarded when the file is smaller than 512 bytes (FILE_TOO_SMALL) or larger than its limit (FILE_TOO_LARGE).
  • Nothing changes when no part was sent yet (NO_CHUNKS_UPLOADED) or a part other than the last is under 5 MB (CHUNK_TOO_SMALL): re-send that part and complete again.

Parameters

string
required
The upload token returned by Chunked Init. It can also go in the upload query parameter.

Rate limits

5 requests per 10 seconds, so several parallel uploads can finish together (RATE_LIMITED, 429).

Response

string
“success” if successful, “error” if not.
object

Errors

  • Blob SDK: blob.put() runs the whole chunked flow for files above 90 MiB