Get Signing Result
This endpoint allows the relying party (RP) to actively query the signing results and obtain the signed document after completion.
Path
GET /sign-requests/:request_id/signed-doc
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:
exchange_code: The exchange_code returned when initiate sign request.jti: Standard JWT ID, a unique identifier for the JWT, must be a UUID.iat&exp: Standard Issued At / Expiration timestamp of JWT. Must issued within 2 minutes.
Example:
Body
Empty
Response
signed_doc_url: Where you can download the signed document.signer_info: an object containing the following information:signer_name: Name of the signer as per the user cert CNsigner_partial_uinfin: The last 4 alphanumerical value of the signer's NRICsigned_at: Unix timestamp in milliseconds of when the user completed the sign request.
exp: Expiration time (in UNIX second) ofsigned_doc_url.
Similar to the successful signing webhook, the signed_doc_urlwill only be valid for 2 minutes. RPs should download the document immediately for their own application. We do not recommend forwarding this URL to the user.
There may be a few scenarios under which you will receive a 400 error:
DOCUMENT_NOT_SIGNED: The user has not signed the document yet and the request has not expired yetREQUEST_EXPIRED: The request has expired without the user signing the document.SIGNED_ACCESS_EXPIRED: The document has been signed, but can no longer be retrieved via this endpoint as the 1h access period has passed.
Sample request
Last updated
Was this helpful?