Cancel Sign Request
This endpoint allows RP to initiate a cancellation to a sign request. RP can cancel any active or expired sign requests created by them.
A cancellation request will be rejected if any of the following conditions are met:
The user has already initiated a sign session (clicked Proceed to Sign and signing QR code is shown)
The document has already been signed
The sign request has already been cancelled
Path
POST /sign-requests/cancel
Headers
Content-Type
application/json
Authorization
<token>
Authorization token
RP should sign the signature parameter into a JWT token as authorization token.
Token Type: Standard JWT (JSON Web Token)
Payload:
request_id: Same as the request id returned during initiate sign requestclient_request: Your application's registered client IDiat&exp: Standard Issued At / Expiration timestamp of JWT. Must issued within 2 minutes.
Example:
Body
Empty
Response
200 OKSign request successfully cancelled
The user has already initiated a sign session (clicked Proceed to Sign)
RP will not be able to cancel and will receive
400 Bad Request
The document has already been signed
RP will not be able to cancel and will receive
400 Bad Request
The sign request has already been cancelled
RP will not be able to cancel and will receive
400 Bad Request
If the request_id is invalid or not found, RP will receive
400 Bad Request.
Sample Request
Last updated