Read asset
A built picture laid on a backdrop color, as it will look on that ground.
A built picture laid on a backdrop color, as it will look on that ground.
x-api-key<token>Scope: manuals:read
id*string^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$regionId*string^[A-Za-z0-9_-]{1,64}$application/json- body
backdrop?array<any>longestSide?integer1 <= value <= 4096An opaque picture, and a link that reads it
application/json- response
requestId*string^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$regionId*stringbackdrop*array<any>picture*curl -X POST 'https://www.chameleonlabs.org/api/manuals/string/assets/string/read' \ -H 'Content-Type: application/json' \ -d '{}'{ "requestId": "string", "regionId": "string", "backdrop": [ 0, 0, 0 ], "picture": { "url": "http://example.com", "expiresAt": "2019-08-24T14:15:22Z", "path": "string", "width": 0, "height": 0 }}List assets GET
The manual's asset index, each picture's link and how each asset stands. The index is the saved one as the saved labels place it: every asset in the labels' order, with the name, label type, count, link, parent and groups the labels give its region, so a new order or a new name shows here once the labels are saved, with no job. What was made of each asset is as the last build left it. An asset whose region is gone is dropped as the labels are saved; while a job runs it is kept, after the rest, until the job's end drops it. The pictures uploaded to the manual are listed apart from the index, oldest first, and placed by their IDs as its pictures are.
Read asset sheet POST
Built pictures side by side on black in one picture, each captioned with its ID. For a first look at many pictures at once, where holes eaten into the art and page left around it stand out on black: each picture is drawn as large as its own cell lets it be and never enlarged, so no scale maps the picture onto a page. Drawn larger than a single read.