Skip to main content
POST
Revert to the catalog optimize preset

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 optimize preset id.

Response

OK

preset
Optimize preset · object

A saved, named set of PDF optimizations (downsample or AI-upscale images, recompress, convert colors to CMYK/gray/RGB, outline text, flatten layers, thicken hairlines, strip junk, resize pages, set trim/crop boxes, add bleed, embed an output-intent ICC profile) that a job applies to the customer's PDF. Workflows point at it from an optimize step, workflow.streams[].steps[] { type: "optimize", config: { presetId } }, and rules from rule.accepts[].flow.optimize.presetId (when flow.optimize.enabled). The preset is read at run time, so edits apply to the next job. The proof sheet also takes its page size from pageResize and its ICC profile from outputIntent. Presets apply to PDFs only, including raster uploads after a Convert-to-PDF step; raster optimize ignores them. The stored shape is NOT the params shape of POST /jobs/optimize: here every group is an object with its own enabled switch and only groups with enabled true are applied (a group without enabled: true does nothing), scaleImages.targetRes is a single DPI number, and flattenLayers is { enabled }. Other keys in the optimize step's config, written in the POST /jobs/optimize params.pdf shape, replace the preset's group of the same name for that step. Groups run as: AI upscale and bleed fill first, then the DynaPDF pass (resize, boxes, conversion, compression, output intent).

reverted
boolean

False when there was no copy to drop.