Start a chunked upload
Open a chunked upload for files of up to 10 GiB with POST /v1/objects/chunked and get the upload token for the next calls.
string
required
The API key for your account. You can find this in your account settings.
upload token that you carry through the next calls:
1
Init
This route. Keep the
upload token.2
Send the parts
Chunked Part, in any order, up to 6 at a time.
3
Complete
Chunked Complete seals the file. Or Chunked Abort to cancel.
Parameters
The query parameters are the same as in Object Post, plusfilename and mime_type: there is no multipart envelope here, so the extension has to come from the query. Requires the blob:write scope, or an upload token, and an active plan.
string
required
The file name, without extension. Same pattern as in Object Post.
string
The original file name, extension included. The stored extension comes from it, then from
mime_type, then falls back to bin.string
Used for the extension only when
filename has none.string
Same as in Object Post.
boolean
Same as in Object Post.
string
Same as in Object Post.
boolean
Same as in Object Post.
boolean
Same as in Object Post.
string
Same as in Object Post.
boolean
Same as in Object Post.
string
Same as in Object Post.
string
Same as in Object Post.
Limits
- File size: up to 10 GiB (10,737,418,240 bytes), or less when a rule or upload token sets a smaller limit.
- Part size: 5 MB minimum (5,242,880 bytes), 32 MB maximum (33,554,432 bytes). The last part may be smaller.
- Parts per file: up to 2048.
- Open uploads per account: 32, counting uploads opened through the S3 gateway (
TOO_MANY_OPEN_UPLOADS, 429). - Rate limit: 5 opens per 10 seconds.
- An account already over its included storage can’t open uploads (
STORAGE_QUOTA_EXCEEDED).
chunk object of the response rather than hardcoding them.Response
string
“success” if successful, “error” if not.
object
Errors
Related
- Blob SDK:
blob.put()runs the whole chunked flow for files above 90 MiB

