Review an unlock response
/api/v1/workspaces/{slug}/unlock-responses/{responseID}/acceptAccept or reject an unlock response
A response moves through the same three states as a certificate request or a
correction: pending, approved, rejected.
| Action | Effect |
|---|---|
POST .../unlock-responses/{responseID}/accept | Approves the response and releases the recipient's existing pending certificate |
POST .../unlock-responses/{responseID}/reject | Keeps the issue pending, mints a fresh link for the recipient, and emails it with your reason so they can resubmit |
Rejecting is not a dead end and does not need undoing: the recipient keeps a working link, and accepting a rejected response releases it as normal.
Accepting releases the issue exactly once: a repeated accept on an
already-released certificate answers 409 unlock_already_released rather than
charging a second credit.
Releasing a recipient who never responded is a separate, deliberate action
(POST /api/v1/workspaces/{slug}/issues/{issueID}/issue). It does not fabricate
an accepted response — the record continues to show that none was accepted.
Authorization
Authorization: Bearer vc_...Requires certificates:write (or full access) and an active Pro seat.
Body parameters
Reject only: