Skip to main content
GET
Get Blob Upload Status for Resume
Returns one direct upload with uploaded_parts, the part numbers already stored. Send only the missing parts after an interruption. Use it to resume an upload. An upload that has expired returns BLOB_UPLOAD_EXPIRED. Scope: blob:write. Accepts an upload token. Upload token: this route also accepts an upload token (Authorization: Bearer vcup_...) instead of an API key.
string
required
The upload ID returned when the upload was started.
string
The workspace ID, when the blob belongs to a workspace. The call acts on the blob of the workspace owner and needs the blob:manage workspace permission, because uploads in progress belong to whoever manages the files. Leave it out to act on your own blob.

Example request

Response

object
The upload and the parts already stored.

Error Responses

string
The error code indicating the reason for failure. Possible values:
  • AUTH_TOKEN_MISSING (401): No Authorization header was sent.
  • API_KEY_INVALID (401): The API key doesn’t exist, was revoked, or its secret doesn’t match.
  • API_KEY_SCOPE_DENIED (403): The key lacks the scope this route needs (blob:read or blob:write); details.required names it.
  • WORKSPACE_PERMISSION_DENIED (403): Only with workspace_id: you’re not a member, or your role lacks the blob permission.
  • WORKSPACE_NOT_FOUND (404): Only with workspace_id: no workspace with that ID, or you’re not a member.
  • BLOB_UPLOAD_TOKEN_INVALID (401): The upload token doesn’t exist, has expired or was revoked (only with an upload token).
  • BLOB_UPLOAD_NOT_FOUND (404): No upload with that ID in this account, or it was already completed or aborted.
  • BLOB_UPLOAD_EXPIRED (410): The upload’s time limit has passed.