Skip to main content
POST
Revert to the catalog preflight profile

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 preflight profile id.

Response

OK

profile
Profile · object

A preflight profile: the checks FileCheck runs on an uploaded file, each with its settings (target), how a failure is judged (severity) and whether it is repaired automatically. There are two kinds. A PDF profile (kind omitted or 'pdf') checks PDFs, and vector and office files once converted to PDF; its checks sit in the sections geometry (geom.), color (color.), text (text.), images (image.) and structure (struct.). A raster profile (kind: 'raster') checks image uploads (JPEG, PNG, TIFF and so on) with the single section raster (raster.). An upload rule points at profiles through rule.accepts[].preflight.profileId: pdf, vector and office accepts need a PDF profile, raster accepts a raster profile. A check runs only when both its section's enabled and its own enabled are true; everything omitted is off. Each check has a severity. reject: a failing file is rejected (shown as a warning instead when the upload rule's onFail is not reject). warn: it passes with a warning. ignore: the finding is recorded but never fails or warns. autofix: the customer is told FileCheck repairs it, and the finding is judged as reject when this file is beyond the repair; autofix is accepted only on checks that have a repair (their description says Autofix: …). Repairs run only in workflows with an autofix step, which repairs every failed check that has a repair whatever its severity, so to stop a repair disable the check. Units are in the field names: _mm millimetres, _pt points (1/72 in), _dpi or dpi pixels per inch, percent, _px pixels, _mb megabytes. Unknown check ids, a check in the wrong section and misspelled settings are refused.

reverted
boolean

False when there was no copy to drop.