- Print
- DarkLight
b2_cancel_large_file
- Print
- DarkLight
Cancels a file upload
Cancels the upload of a large file, and deletes all of the parts that have been uploaded.
This will return an error if there is no active upload with the given file ID.
API Versions
v1 Application Keys (July 26, 2018)
Incompatible change — After calling b2_authorize_account with an application key that does not have the right permissions, this call will return a 401 Unauthorized.
v1 Original release (September 22, 2015)
PLEASE NOTE:
This API endpoint can be called using a GET
request by converting the parameters in the request body to query parameters.
An account authorization token, obtained from b2_authorize_account. The token must have the writeFiles
capability.
This is required if the bucket containing the file is not public. It is optional for buckets that are public.
The request succeeded.
The ID of the file whose upload that was canceled.
The account that the bucket is in.
The unique ID of the bucket.
The name of the file that was canceled.
status | code | description |
---|---|---|
400 | bad_bucket_id | The requested bucket ID does not match an existing bucket. |
400 | bad_request | The request had the wrong fields or illegal values. The message returned with the error will describe the problem. |
The numeric HTTP status code. Always matches the status in the HTTP response.
A single-identifier code that identifies the error.
A human-readable message, in English, saying what went wrong.
status | code | description |
---|---|---|
401 | bad_auth_token | The auth token used is not valid. Call b2_authorize_account again to either get a new one, or an error message describing the problem. |
401 | expired_auth_token | The auth token used has expired. Call b2_authorize_account again to get a new one. |
401 | unauthorized | The auth token used is valid, but does not authorize this call with these parameters. The capabilities of an auth token are determined by the application key used with b2_authorize_account. |