Registry API
Content objects
Upload and fetch content objects addressed by their SHA-256.
An asset’s bytes are stored once, as a content object identified by its content hash. HEAD checks whether an object exists before you upload it.
Operations
| Request | What it does |
|---|---|
| POST /api/objects | Store a content object |
| GET /api/objects/{sha256} | Fetch a content object |
| HEAD /api/objects/{sha256} | Check that a content object exists |
Operations are exactly those in the committed OpenAPI document (packages/workloom-api/openapi.json), which matches the route definitions; this site checks its list against both. Paths are under the API host. Public, approved packages and profiles can be read without a token; everything else needs one.