Approve a requestpost https://your-protect-instance.example.com/api/rest/v1/requests/approveThis endpoint approves a request. Required role: RequestApprover.Body ParamssignaturestringrequiredThe signature of the request approval, in the form base64(ecdsa_sign(sha256([hex(sha256(req1_metadata)),hex(sha256(req2_metadata)),...hex(sha256(reqN_metadata))])))commentstringrequiredA comment field for the request approval, can be used to indicate the approver, or reason for approval.requestIdsarray of stringsuint64; Deprecated: use the ids parameter insteadrequestIdsADD stringidsarray of stringsrequireduint64; The IDs of the requests to approveids*ADD stringasyncbooleanProcess the requests asynchronously (in the background). Use for large numbers of approvalstruefalseResponses 200A successful response. 400Bad Request: indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing) 401Unauthorized: indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource 403Forbidden: indicates that the server understands the request but refuses to authorize it 404Not Found: indicates that the server cannot find the requested resource 500Internal Server Error: indicates that the server encountered an unexpected condition that prevented it from fulfilling the request 503Service Unavailable: indicates that the server is not ready to handle the request. defaultAn unexpected error response.Updated about 2 months ago Force kill a requestCreate a simple outgoing request (using addresses)Did this page help you?YesNo