Approve or deny one pending publishing approval request owned by this Account. The API key's creator must retain approval-management access for the Account.

Approval starts publishing the Project on behalf of the original requester. The review body contains only the decision and, for a denial, an optional reason. Approval does not wait for publishing to finish: read the request until data.status is fulfilled or fulfillment_failed. If publishing fails, data.execution.message explains what to do next.

Send the list item's reviewEtag or the detail response's complete opaque ETag unchanged in If-Match. Reload after an ownership change and use the new tag, even if no new request event was recorded.

A missing header returns 428 (precondition_required); a malformed or weak value returns 400 (invalid_request); a tag made stale by a new request event or a change to the visible Workspace returns 412 (precondition_failed); a current tag on a request that is no longer pending returns 409 (request_already_resolved); and a decision that the request cannot accept returns 409 (conflict).

A successful review returns 200 with the updated request, its ordered public event history, a new ETag, and Cache-Control: no-store, no-transform.

A read made immediately after a review can briefly return the request's previous state. If the response is lost, wait briefly and read the request again. If it is resolved, do not retry; if still pending, retry only with the latest read's ETag. The returned ETag changes with the request's event history or visible Workspace, but not with every change to other response fields.