Skip to main content
The content is more than a few hundred words, or you are enforcing many pieces at once: newsletters, client letters, reports, proposals, disclosures, landing pages. Async returns immediately with a job_id; you poll for the verdict.

Prerequisites

  • An API key (Quickstart).
  • Content as plain text. Convert PDFs and DOCX to text before sending. Policy import accepts files; content enforcement takes text.

The flow

After completed, apply confident fixes and escalate the rest. When revalidation_recommended is true, re-enforce the fixed text once before publishing. For the Pass / Fix / Block / Escalate decision table, see Act on Each Verdict.

Code

Set mode to "async".

Reading the result

Completed jobs nest these fields under result (they may also appear at the top level on some responses):

Gotchas

  • Poll until completed or failed. There is no published fixed completion time.
  • Re-enforce after Fix All when revalidation_recommended is true. Fixes to adjacent lines can interact.
  • Quotes and line numbers refer to the text exactly as you sent it. Do not normalize whitespace between submit and fix.
  • Batch carefully. Submit and poll within the limits configured for your account. Back off on 429 responses.

Next

Act on Each Verdict

Pass / Fix / Block / Escalate after the job completes.

Export Activity

Pull verdicts for every document you have enforced.