Bulk-clear (soft-archive) persisted edits
Clear active edits in bulk — sets cleared_at, removing them from future overlays (ENG-3219).
A CONTENT edit pins its file’s body against every future regen until cleared; recovering a set of manually-patched files previously meant one DELETE per edit id. Rows are kept for audit, same as the single-edit DELETE. ADD-edit prompt cleanup intentionally matches the single-edit endpoint.
Authorizations
API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.
Body
Response
Successful Response