Approve a pending version with custom code — the second pair of eyes (site_tags.approve)

POST 
/api/integrations/website/sites/:site/tags/versions/:version/approve

Doc 106 §26-2, CMP-5. In a workspace with two or more active members (and the four-eyes rule on), a version with custom HTML/JS waits as pending until another member approves it. The approver may not be its submitter nor the last author of its draft (403 own_version), must have said the two-factor code in the last 15 minutes (403 step_up_required, see stepUp), and the platform scan must still find nothing (422 custom_findings). The version then goes live. Audit row website.tags_approved.

Request

Responses

200

The site's tags, with the version now live.

403

Authenticated but not allowed.

404

Resource not found (or not visible to the current tenant).

422

The request failed validation.