Source Code Bundles
Lists information about large file uploads that have been started, but have not been finished or canceled.
Uploads are listed in the order they were started, with the oldest one first.
This call returns at most 1000 entries, but it can be called repeatedly to scan through all of the uploads for a bucket. Each time you call, it returns a "nextFileId" that can be used as the starting point for the next call.
Request HTTP Headers
The account authorization token returned by
Request HTTP Message Body Parameters
The bucket to look for file names in.
The first upload to return. If there is an upload with this ID, it will be returned in the list. If not, the first upload after this the first one after this ID.
The maximum number of files to return from this call. The default value is 100, and the maximum allowed is 100.
Response HTTP Status 200
List of unfinished large files as JSON:
An array of objects, each one describing one unfinished file. (See below.)
What to pass in to startUploadId 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 ID of an actual upload, but using it is guaranteed to find the next upload.
And each of the files is:
The name of this file.
Your account ID.
The bucket that the file will be in.
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 started. 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: