Get committed blob bytes | API reference

Description

Streams a committed blob's encrypted bytes, with its byte length and SHA-256 digest in response headers so the client can verify them. Requires read access through at least one active attachment binding's document.

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
`blobId`	path	string	required UUID

Responses

200 OK

application/octet-streambytes

raw bytes

Response headers

Name	Type	Details
`x-tearleads-blob-byte-length`	string	required at most 16 characters decimal digits
`x-tearleads-blob-id`	string	required not empty
`x-tearleads-blob-sha256`	string	required not empty
`content-length`	string	optional

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.

Blob byte length headers decode to JavaScript safe integers.