Skip to main content
POST
Preview. This endpoint is available to organisations in the Wordsmith MCP pilot. Other organisations receive 403 mcp_not_enabled. See the preview overview.
Writes the amendments of the findings you choose into the reviewed documents as tracked changes. The output is a new file: a DOCX when the amendments change one document, or a ZIP of one DOCX per document when they change several. By default it includes every issue that has a proposed amendment. Pass finding_ids to choose a subset. A finished review already has a redline of every proposed amendment in its redline_file_id. Use this endpoint when you want only some of them. The new file does not replace the review’s redline_file_id: read its id from the operation’s result. It lives with the review, so anyone who can read the review can read it. It runs as an operation, because a large document can take a few minutes. It works on playbook and instructions reviews whose reviewed documents include a DOCX.

Authentication

Requires an API key, or an OAuth token with reviews:write. Reading the new file needs files:read.

Path parameters

string
required
The review id. The review must be completed.

Headers

string
A unique key for this request, such as a UUID. A repeat with the same key and body within 30 days returns the same operation and makes no second file.

Body parameters

The body is optional: an empty body takes every default.
string[]
The findings whose amendments to apply, from List Findings. Each must belong to this review and propose an amendment. Defaults to every finding whose status is issue and that proposes an amendment.
integer
default:"0"
Seconds to wait for the redline before responding, from 0 to 20. A short document often finishes inside 20.
string
A public HTTPS URL that receives a signed operation.succeeded, operation.failed or operation.cancelled event when the redline is ready. API keys only.

Response

Returns 202 with an operation of type review_redline. Its resource is the review. A repeat with the same Idempotency-Key returns 200 with the same operation. When status is succeeded, result is { "file_id" }: the new tracked-changes DOCX, or a ZIP of DOCX files when the amendments changed more than one document. Read its content_type with Get File before you open it. Running this endpoint again makes a new file. When none of the chosen amendments could be applied, the operation fails with error.code no_amendments. When the redline could not be written, it fails with redline_failed, which is retryable. Cancelling the operation stops it: a file made before the cancel arrived is deleted, and the operation ends cancelled.

Errors