Skip to main content
Acts on findings from the stored report for this content: accepted issue ids rewrite the stored body with the suggested replacement, ignored issue ids record a dismissal without touching the copy. Both are persisted atomically with the body write, and decisions are carried across re-checks — a fixed or dismissed finding does not come back as open. Scope required: compliance:write Also requires the dealership’s Compliance Checking plan feature (Pro+ / add-on).

​
Path parameters

​
string
required
UUID of the content.

​
Body

​
string[]
Findings to fix. Each id comes from the stored report (GET /content/{id}/compliance → report.issues[].id); the suggested replacement is applied to the stored body.
​
string[]
Findings to dismiss. Recorded with the reason; the copy is untouched.
​
string
Why the ignored findings are acceptable (stored with the dismissal).
​
boolean
Must be true to rewrite content that is already published.
At least one of issue_ids or ignore_issue_ids is required. Send an Idempotency-Key header to make retries safe.

​
Response

​
boolean
Whether any accepted fix changed the stored body.
​
object[]
Accepted findings that were rewritten, with the text replaced and how many occurrences changed.
​
string[]
Issue ids recorded as dismissed.
​
object[]
Requested findings that could not be applied, each with a reason (for example, the flagged wording is no longer present).
​
boolean
The body changed after the report was produced — re-run the check before trusting the remaining findings.
A 409 with code stale_content means the article body changed between reading the report and applying it — nothing was written. Re-run the compliance check for a fresh report, then retry.
Published content is refused unless allow_published: true is passed — rewriting a live page is a deliberate choice.
Last modified on August 26, 2026