Accept Success Signing Webhook
Last updated
Was this helpful?
Last updated
Was this helpful?
Upon successful signing, Sign will notify the relying party (RP) via a webhook. The RP must implement and expose a webhook endpoint on their server to receive this notification. The webhook will inform the RP that a signing transaction has been successfully completed and provide the URL to download the signed document.
A POST request to the webhook URL that was provided to us during your .
A JSON object with only 1 field token .
The token is a standard with payload:
request_type: Always signed_doc_url
signed_doc_url: Where you can download the signed document. This link will expire after 2 minutes.
request_id: Same as the request id returned during initiate sign request
iat & exp: Standard Issued At / Expiration timestamp of JWT. The expiry of the token is set to 2 minutes. The signed_doc_url will expire within the exp as well.
RP are required to implement token validation by fetching the , and verify the signature, expiration, and claims contained in the JWT.
RP are required to download the document immediately as the signed_doc_url will expires in 2 minutes. We do not recommend RP to send the signed_doc_url to user for the same reason.
Example:
It is sufficient to respond with only 2XX HTTP status code without any response body.
Singpass will perform automated retries of webhook calls in the case of timeouts or certain errors.
RP are required to respond to the webhook request within 2 seconds.
We strive to maintain consistent egress IPs, but please note that they are subject to change with short notice.
Staging:
54.169.20.186
Production:
18.143.229.39
54.179.76.90
3.0.39.45