Complete Asset Upload
Step 3 of 3. Call after the PUT to upload_url returns 2xx. The
server reads the uploaded object’s size and MD5 from blob storage,
records them on the asset row, and hands the asset to the ingest
pipeline. The response carries the current asset status; clients
poll GET /v1/assets/{id} until status is ready or failed.
Authorizations
Personal Access Token, sent verbatim as pat_<32 chars>. PATs are
minted from the Chief settings UI.
Headers
Project identifier scoping the request. Required on every
project-scoped public endpoint. Missing or malformed values respond
with HTTP 400 and code publicapi.tenancy.project.missing.
^project_[a-z0-9]{20}$Path Parameters
Asset identifier returned by POST /v1/assets.
^asset_[a-z0-9]{20}$Body
Body of the asset-complete call. Empty in v1; reserved as a named schema so future ingest hints can be added additively.
Response
Asset state.
^asset_[a-z0-9]{20}$Asset lifecycle. Progresses uploaded -> ingesting -> ready, or terminates at failed on any extraction error.
uploaded, ingesting, ready, failed