> For the complete documentation index, see [llms.txt](https://docs.developer.singpass.gov.sg/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developer.singpass.gov.sg/docs/singpass-developer-docs/sign-with-singpass/for-relying-parties/api-documentation/document-signing-v1/sign-docs.md).

# User Journey (V1)

{% stepper %}
{% step %}

### On the organisation's webpage, click / tap on the 'Sign' button

<figure><img src="https://3146998070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYUqAI09tBnmTJ02qSo9L%2Fuploads%2Fgit-blob-a0154ad2e6f463ba351d4179f0c06ab2d7909fac%2FSafari%20(Catalina)%20-%20Light.png?alt=media" alt=""><figcaption><p>Sample organisation's webpage</p></figcaption></figure>
{% endstep %}

{% step %}

### Scan the QR code with your Singpass App

<figure><img src="https://3146998070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYUqAI09tBnmTJ02qSo9L%2Fuploads%2Fgit-blob-1a4c761006ea3b1ef9ed09ac3b6c3031bd1a5b88%2FScan%20QR.png?alt=media" alt=""><figcaption><p>Screen showing QR (Desktop &#x26; Mobile views)</p></figcaption></figure>
{% endstep %}

{% step %}

### Approve or Reject on your Singpass App:

Check that the reference codes on your desktop and mobile screens are the same.

Tap *Approve* to sign the document, or *Reject* to cancel the signing.

<figure><img src="https://3146998070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYUqAI09tBnmTJ02qSo9L%2Fuploads%2Fgit-blob-65ea26ab37bf9f17c8dc34502cab0ed450e5f6a7%2FConsent%20(3).png?alt=media" alt=""><figcaption><p>Screens shown after QR is scanned (Desktop &#x26; Mobile views)</p></figcaption></figure>
{% endstep %}

{% step %}

### Signing complete!

Return to the organisation's webpage to complete the rest of the process (if any).

<figure><img src="https://3146998070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYUqAI09tBnmTJ02qSo9L%2Fuploads%2Fgit-blob-a4c49d3ffa8cec203c9366febad16cf58c6bb22b%2FDocumentSigned%20(2).png?alt=media" alt=""><figcaption><p>Successful signing (Desktop &#x26; Mobile views)</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## You may have some questions...

<details>

<summary>What is the reference code for during the signing?</summary>

The purpose of the reference code is to allow users to verify that they are signing the correct document, when the code on their Singpass App matches that which is shown on the organisation's webpage.

</details>

<details>

<summary>How can I download my document after signing?</summary>

You may return to the organisation who has sent you this document for the signed copy.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.developer.singpass.gov.sg/docs/singpass-developer-docs/sign-with-singpass/for-relying-parties/api-documentation/document-signing-v1/sign-docs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.