POST Upload Finished

POST /uploads/(uid)/finished

Notify the server that all files have been uploaded for the given upload session, and processing can begin. The request must include the uploaded parameter, which specifies the number of files that were uploaded, and the number of parts in each file. The server uses this information to validate that it received every part of every file that the client sent.

  • uid (string) – Unique upload session identifier.
Request Headers:
Request JSON Object:
  • uploaded (array) – array containing the number of parts \(M\) for every uploaded file \(N\).
Status Codes:
  • 202 Accepted – The server has validated all of the uploaded data, and will begin the parsing process.
  • 400 Bad Request – “Upload incomplete” The server did not receive all of the file parts specified in the uploaded parameter. Parsing will not begin until the missing parts have been uploaded and POST /uploads/(uid)/finished is called again.
  • 400 Bad Request – “Client confused” The server received more file parts than those specified in the uploaded parameter. Parsing will not begin unless POST /uploads/(uid)/finished is called again with the correct part counts in uploaded.
Response Headers:
Response JSON Object:
  • missing (array) – array containing a [fid, pid] tuple for every file part that wasn’t uploaded successfully.

See Also