Commit bytes as a blob — one multipart request at or under the D7 threshold

POST

/api/blobs

Maintainer:Not configured

OperationId:commit_blob

Form fields: file (the bytes; its content type is the media type committed),
home_table (kb_contexts or kb_cogmaps — a blob needs a home, D2), home_id (the
anchor's id). The caller acts as themselves: owner is the authenticated profile.

The threshold is enforced WHILE the file field streams, so an over-threshold body is
refused before it is ever fully buffered, and the refusal names the vocabulary — the
threshold in force and the segmented path beyond it. Cap and allowlist stay the SQL
wrapper's authority: the substrate write passes this config's numbers through, and a
refusal from there surfaces verbatim (blob_service::map_commit_err).

Request

Authorization

JWT Bearer

Add the parameter

Authorization

to Headers

Example:

Authorization: ********************

Header Params

Body Params multipart/form-data

Responses

🟢200OK

application/json

Committed (or dedup-hit) blob

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

Request Example

Shell

JavaScript

Java

Swift

curl --location --request POST '/api/blobs' \
--header 'X-Temper-Surface;' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Example 1

{
    "blob_id": "8249af2f-dd23-416e-b9c4-6cb13a792190",
    "content_bytes": 0,
    "content_hash": "string",
    "content_type": "string",
    "deduped": true,
    "estate_scope_disclosure": "string"
}

Modified at 2026-09-04 22:37:55

List the blobs the caller can read (optionally scoped to one home)

Begin a segmented upload — declare the home and media type, get the session id