This endpoint can be used for creating a resumable upload endpoint, allowing for the robust transfer of large files to Redivis.
Resumable uploads can be quite complex. It is highly recommended to use one of the client libraries to upload your files (and handle resumable uploads for you), rather than calling this endpoint directly.
Edit access to the table's dataset is required. Your access token must have one of the following scopes:
The request body must be empty.
Returns the url and id for the resumable upload.
The general process for performing a resumable upload is to send the file in a series of chunks, via
PUTrequests to the url returned when creating the resumable upload. For each request, specify the
Content-Rangeheader to inform which chunk is currently being uploaded, and provide the content of the chunk in the request body.
Resumable uploads expire after 24 hours.
You should provide the current chunk content in the request body.
Upon successfully transferring a chunk, the response body will be empty with a status of 200.
If an upload request is terminated before receiving a response, or if you receive a
500Service Unavailable response, then you need to resume the interrupted upload. To resume an interrupted upload:
- 1.To request the upload status, create an empty PUT request to the resumable session URI.
- 2.Add a Content-Range header indicating that the current position in the file is unknown. For example, set the
*/2000000if your total file length is 2,000,000 bytes. If you don't know the full size of the file, set the
- 3.Send the request.
- 4.Process the response.A 200 OK or 201 Created response indicates that the upload was completed, and no further action is necessary. A 308 Resume Incomplete response indicates that you need to continue uploading the file.
- 5.If you received a 308 Resume Incomplete response, process the response's Range header, which specifies which bytes Cloud Storage has received so far. You will use this number in the next step. The response does not have a Range header if Cloud Storage has not yet received any bytes. For example, a Range header of bytes=0-42 indicates that the first 43 bytes of the file have been received.
- 6.Now that you know where to resume the upload, continue uploading the file, either by sending the remaining data or by sending the next chunk. Include a Content-Range header indicating which portion of the file you are sending. For example, Content-Range: bytes 43-1999999/2000000 indicates that you are sending bytes 43 through 1,999,999.