Approve or deny one pending public publish enablement request owned by this Account. The API key's creator must retain approval-management access for the Account. Requests remain reviewable by the Account that received them after a Project moves.

Approval grants a Project-specific public publishing override; it does not create or publish a deployment. If the Project's current Account differs from the request's Account, approval records fulfillment_failed rather than granting the override. Other eligibility failures return 409 (conflict) and leave the request pending. Projects that are no longer available for review return 404 (not_found).

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); and a current tag on a request that is no longer pending returns 409 (request_already_resolved).

A successful review returns 200 with the updated request, its ordered public event history, a new ETag, and Cache-Control: no-store, no-transform. Check data.status to distinguish fulfilled from fulfillment_failed; an accepted approval does not guarantee that the override was granted.

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.