Approve or deny an access request

PUT 
/access-requests/:request_id

Handles a pending access request. The request body requires Action (approve or deny) and Comment. The caller must have the required role authorization and owner or editor access to the resource, with permission to grant the requested access type. The access request must exist and remain in requested status. For dataset approvals, domain access may also be required. Approving grants the requested resource access and records the approval, while denying updates the request status and notifies the requester.

Request

Responses

200

Request approved or denied. Body is Message only (HandleAccessRequestResponse).

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

400

Validation or authorization failure. Body is {"Message": " - "}. Common codes: GE-1007 (invalid Action), IPV-1002 (RequestId not found), AUTH-1010 (not owner/editor or cannot grant AccessType), GE-1086 (already handled or requester already has access), AUTH-1003 (dataset approve missing domain access), GE-1034 (resource id mismatch on approve check).

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

500

Backend failure. Body is {"Message": " - "} (typically GE-1085 via EMF-1001), including grant-permission Lambda failures or unbound response if DynamoDB write fails. Missing Comment/Action in body raises KeyError and returns 500.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers