This endpoint is used to append a chunkedFilePart to a chunked file.
Chunked file parts must provide an offset and a size along with content. The first chunked file part must have offset 0. You may add
the same chunked file part multiple times to retry a failed import. When retrying, you must use the same offset and size. You may add
chunked file parts out of order.
The body of the request is an HTTP form with the Content-Type header set to multipart/form-data, and contains 2 parts: chunkedFilePart
for the chunk properties, and fileChunk for the data.
The chunkedFilePart must have the Content-Type header set to application/json and is similar to other entity types. It specifies the
offset and size of the chunk.
The fileChunk contains the file to be imported. Its Content-Type header must correspond to the file’s data type.
For example, for a .csv file, the Content-Type header for the fileChunk should be text/csv.
api.file-manager.writeBearer authentication header of the form Bearer <token>, where <token> is your auth token.
multipart/form-data No Content