Source Code Bundles
Lists the parts that have been uploaded for a large file that has not been finished yet.
This call returns at most 1000 entries, but it can be called repeatedly to scan through all of the parts for an upload.
Request HTTP Headers
The account authorization token returned by
Request HTTP Message Body Parameters
The ID returned by
The first part to return. If there is a part with this number, it will be returned as the first in the list. If not, the returned list will start with the first part number after this one.
The maximum number of parts to return from this call. The default value is 100, and the maximum allowed is 1000.
Response HTTP Status 200
List of parts as JSON:
An array of objects, each one describing one part. (See below.)
What to pass in to startPartNumber for the next search to continue where this one left off, or null if there are no more files. Note this this may not be the number of an actual part, but using it is guaranteed to find the next file in the bucket.
And each of the parts is:
The file ID for uploading this file.
Which part this is.
The number of bytes stored in the part.
The SHA1 of the bytes stored in the part.
The MD5 of the bytes stored in the part. Not all parts have an MD5 checksum, so this field is optional, and set to null for parts that do not have one.
This is a UTC time when this part was uploaded. It is a base 10 number of milliseconds since midnight, January 1, 1970 UTC. This fits in a 64 bit integer such as the type "long" in the programming language Java. It is intended to be compatible with Java's time long. For example, it can be passed directly into the java call Date.setTime(long time).
If possible the server will return a JSON error structure. Errors include:
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)