Use the upload API from your own client
UseGET workspaces/{workspace}/upload-policy to choose the transfer method.
For a resumable upload, send a file name, byte size and stable request key to
POST workspaces/{workspace}/upload-sessions. You can pass direct: true when
the client supports signed S3 uploads. The session response includes
transport (local or s3-multipart), chunkBytes and acceptedParts.
Part indexes start at zero in the Studio API. In a local session, send bytes to
PUT .../parts/{part}. In a direct session, call POST .../parts/{part}/sign
with the lowercase hex sha256, upload the exact part with the returned headers,
then send the quoted S3 ETag as etag to POST .../parts/{part}/receipt. Call
POST .../complete after all parts are accepted. Retrying completion of an
accepted session returns the same file.
Request and state reference
Paths below are relative to the active API base. Add your usual JSON headers and authentication to Studio requests. The signed storage request uses only the headers from the signer.
A client that supports both transports can start with this JSON request.
parent is an optional folder ULID. The file name, size and destination must remain consistent when retrying the same key.
chunkBytes, send only parts that are absent from acceptedParts, then complete. After a lost receipt response, check status before retrying. After a lost completion response, repeat the completion with the same session. If the session expires, start a new operation and explicitly request the source file again if the client lost it.