GEgetanana
Content Management

Apply Revision Suggestion Route

Changed on

Apply one suggestion now: a live page publishes it in its current visibility, a draft stays a draft. No separate publish step.

post/api/v1/content/revision-suggestions/{suggestion_id}/apply

Request

Path parameters

suggestion_idstring uuid required

Request body

replacementstring nullable

Response

Successful Response

idstring uuid required
review_idstring uuid required
sequenceinteger required
original_textstring required
proposed_textstring required
rationalestring required
evidenceobject nullable
experiment_idstring uuid nullable
status'proposed' | 'applied' | 'rejected' | 'conflict' | 'failed' required

Where one agent-proposed KC revision suggestion stands.

PROPOSED → APPLIED / REJECTED / CONFLICT / FAILED. There is no in-flight state: an apply is one transaction, so it either commits APPLIED or rolls back. FAILED may be retried (or rejected); CONFLICT is final — the page changed under it.

approved_textstring nullable
applied_atstring date-time nullable
decided_atstring date-time nullable
errorstring nullable

Changes