Sign with Singpass
Singpass Developer DocsAsk a Question
  • START HERE
    • Overview of Sign
    • How do our Digital Signatures work?
    • Frequently Asked Questions
  • FOR USERS
    • How to sign
    • Verifying Sign with Singpass Signatures
      • Loading Singpass Root Signing Certificate
  • FOR RELYING PARTIES
    • Use Cases
    • Getting Started
      • How to Onboard our API
      • Digital Signing Partners
        • Docusign
        • Tungsten Automation
        • OneSpan
        • Tessaract Technologies Pte Ltd
        • Netrust Pte Ltd
        • Modus Consulting
        • Redoc.co by Real Estate Doc Pte Ltd.
        • CrimsonLogic
        • Zoho Sign
        • Securemetric Technology Pte. Ltd.
        • Rently Pte. Ltd.
    • API Documentation
      • Document Signing V3
        • Initiate Sign Request
        • Redirect From Sign with Singpass
        • Accept Success Signing Webhook
        • Get Signing Result
        • JWKS Specification
        • Sign Portal
      • Document Signing V1
      • Transaction Signing
        • Embedding Singpass JS
        • Init Transaction Signing
        • Exchange Transaction Signature
    • UX Guidelines
      • User Journey Illustration
    • Support
Powered by GitBook
On this page
  • Change log
  • High-level integration flow
  • Production and staging URLs

Was this helpful?

  1. FOR RELYING PARTIES
  2. API Documentation

Document Signing V3

Last Updated: 2 June 2025

PreviousAPI DocumentationNextInitiate Sign Request

Last updated 7 days ago

Was this helpful?

V3 continues our mission to enhance the convenience and security of digital signing in Singapore. It significantly reduces technical complexity, ensuring faster and safer implementation, and provides greater access to digital signing to businesses and citizens across various aspects of their lives.

Change log

Date
Changes

2 June 2025

Initial version

High-level integration flow

Relying Parties (RPs) will send us the document, and then redirect the user to our Sign portal to perform the signing. Sign will then notify the RP of a successful signing via their webhook, from which RPs can retrieve the signed document.

RPs are expected to implement the following steps referenced from the diagram above:

Step
Component
Summary
Specifications

1

Backend

Send raw document to Sign with Singpass and get signing_url

2

Frontend

Redirect user to Sign with Singpass

3.1

Frontend

Accept redirect from Sign with Singpass

3.2

Backend

Accept success signing webhook

4

Backend

Get signing result

5

Backend

Download signed document

N/A. Just fetch the signed document from signed_doc_url

0

Backend

JWKS specifications

Production and staging URLs

Staging Base URL: https://staging.sign.singpass.gov.sg/api/v3

Production Base URL: https://app.sign.singpass.gov.sg/api/v3

Redirect user to the via the signing_url retuned in step 1. RP should follow to render the "Sign with Singpass" button.

Initiate Sign Request
Redirect From Sign with Singpass
Accept Success Signing Webhook
Get Signing Result
JWKS Specification
UX Guidelines
Sign Portal
Sign V3 High-level integration flow