Regenerate stale assets
Starts regenerating the assets that are stale and the regions that have none.
Starts regenerating the assets that are stale and the regions that have none.
x-api-key<token>Scope: manuals:write
id*string^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$The job as it stands; poll the job route until it is no longer running
application/json- response
job*|nullcurl -X POST 'https://www.chameleonlabs.org/api/manuals/string/jobs/regenerate-stale'{ "job": { "id": "string", "kind": "breakdown", "status": "running", "startedAt": "2019-08-24T14:15:22Z", "stoppedAt": "2019-08-24T14:15:22Z", "error": "string" }}Start publish POST
Publishes the deck for everyone or for its owner, or moves a published deck. On a manual that is unpublished, or published at the visibility sent, this starts a `publish`: the pack is built from the cards and assets as they are saved. A publish needs `cardsVersion`, the version of the cards its caller read and means to publish, which is the number in the cards' ETag: cards saved since are refused with `stale-version`, to be read again first. On a deck published at the other visibility it starts a `change-visibility`: the deck as it is published moves, and the saved cards take no part, so `cardsVersion` is not needed and one sent is not looked at.
Start unpublish POST
Takes the published deck away.