Source Code Bundles
Converts the parts that have been uploaded into a single B2 file.
After you have uploaded the parts, use this call to combine the uploaded parts into one large file.
It may be that the call to finish a large file succeeds, but you don't know
it because the request timed out, or the connection was broken. In that case,
retrying will result in a 400 Bad Request response because the file is already
finished. If that happens, we recommend
Request HTTP Headers
An account authorization token, obtained from
Request HTTP Message Body Parameters
The ID returned by
A JSON array of hex SHA1 checksums of the parts of the large file. This is a double-check that the right parts were uploaded in the right order, and that none were missed. Note that the part numbers start at 1, and the SHA1 of the part 1 is the first string in the array, at index 0.
[ "40d2b810f4b3978444b98d44a01cbc2680432726", "956a86f77f2fd6181fcec963d3244689b720d845" ]
Response HTTP Status 200
Large file successfully finished. The JSON response will contain:
The name of this file, which can be used with
Your account ID.
The bucket that the file is in.
The number of bytes stored in the file.
Large files do not have a SHA1 checksum. The value will always be "none".
The MIME type of the file.
The custom information that was uploaded with the file. This is a JSON object, holding the name/value pairs that were uploaded with the file.
This is a UTC time when this file 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).
Large file not finished.
If possible the server will return a JSON error structure. Errors include: