Upload multipart blob part bytes through the API | API reference

Description

Uploads one part's encrypted bytes through the API, for object stores that cannot sign direct upload URLs. Only the stage's owner may call it, and stores that do sign URLs reject this route. The part's declared byte length and SHA-256 headers must match the bytes sent.

Authentication

Requires a signed-in session: the client sends its session token as a bearer token in the Authorization header.

Parameters

Name	In	Type	Details
`stageId`	path	string	required UUID
`partNumber`	path	integer	required at least 1
`x-tearleads-blob-part-byte-length`	header	string	required 1 to 9 characters decimal digits
`x-tearleads-blob-part-sha256`	header	string	required exactly 64 characters lowercase hexadecimal
`x-tearleads-blob-upload-id`	header	string	required not empty

Request body

application/octet-streambytes

raw bytes

Responses

200 OK

application/jsonUploadMultipartBlobPartResponse

Confirms a part uploaded through the API byte route.

3 fields

partMultipartBlobStagePartrequired
stageIdstringrequired
uploadIdstringrequired

Other fields are allowed.

Other responses

Status	Meaning	Body
400	Bad Request	`application/json`ErrorResponse
401	Unauthorized	`application/json`SessionFailureResponse
403	Forbidden	`application/json`ErrorResponse
404	Not Found	`application/json`ErrorResponse
409	Conflict	`application/json`ErrorResponse
500	Internal Server Error	`application/json`ErrorResponse
503	Service Unavailable	`application/json`ErrorResponse

Additional rules

The server also enforces these rules, which the schema above cannot express.

Declared multipart part byte length is at most 33554432.