Skip to main content
POST
Revert to the catalog workflow

Authorizations

Authorization
string
header
required

Your secret key as a bearer token, e.g. Authorization: Bearer sk_live_…. Secret keys are server-side only.

Path Parameters

id
string
required

The catalog workflow id.

Response

OK

workflow
Workflow · object

A workflow is the fulfilment pipeline for a product: what happens to a customer's upload from the moment it is dropped on the product page until the print-ready file reaches the shop. Intake runs first, while the customer waits: it points at an upload rule (which file kinds, how many files or slots, and per kind the preflight profile that checks them and whether a failing file is rejected). When the trigger fires (order placed, upload accepted, proof approved or a manual run), each accepted file runs the stream for its kind (autofix, convert an image to PDF, optimize with a preset, split pages); then merge can combine the files, and delivery sends the result to the account's destinations. Proofing optionally shows the customer a soft proof at the end of intake, and can hold the job until they approve it. Rules, preflight profiles, optimize presets, destinations and scenes are separate records referenced by id; product mappings and the embedded upload widget point at a workflow by its id. A job copies the workflow when it is created; jobs that already hold files keep the version they started with. A minimal create body is { "title", "intake": { "ruleId" } } plus one stream per file kind the rule accepts; without streams files are delivered as they left intake.

reverted
boolean

False when there was no copy to drop.