Append an asset version
Uploads a fully rendered image — with all edits already applied to its pixels — above the original version. An append is accepted only while the original is current; replace the current derived version through its replacement endpoint instead. Exact duplicates store nothing. Metadata is copied from the original, so retained bytes may differ from uploaded bytes.
Authorizations
Query Parameters
Optional response expansion. The single accepted value is variants: without it each row's version_urls carries only its lean thumbnail rung; with it, every rung plus the signed exact-byte original. Accepts multiple include= query params or a single comma-delimited value. Unknown values return 422.
Body
JPEG or PNG bytes with all edits and orientation already applied to the pixels, at most 100 MiB. The metadata-finalized file must also remain within that limit. The part's Content-Type declares the expected format; the format detected from the bytes is authoritative, and a concrete declared type that disagrees with it returns 422.
Response
The upload duplicates the current version (same kind, params, and bytes); that version is returned and nothing new is stored.
One rendering in an asset's retained version chain.
Base64-encoded SHA-256 hash of this rendering's stored bytes, for comparing a locally computed hash against the chain (e.g. when reconciling an ambiguous create failure). Not unique: identical bytes may legitimately appear at different positions or on other assets. Transitionally null for roots written during the column's rollout window, until a follow-up backfill lands.