> 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/getting-started/user-journey.md).

# User Journey

User Journey Submission

When creating an application in the **Production environment**, you are required to submit a **User Journey** showing how your digital service will integrate with Singpass APIs.

Step 1: Download the relevant User Journey template

Please download and complete the User Journey template that is relevant to your use case:

#### Use Case Options:

1. **Myinfo API** - Use this API to retrieve user information for **form filling** or **registration** purposes.

{% file src="/files/zQ92KpQaEamUqcQ9ApLl" %}

2. **Login API** - Use this API as a secure alternative login method to your existing authentication or verification flow.

{% file src="/files/6LHGGISQ5QIdRB8FENtN" %}

3. **Myinfo Business** - Retrieve business-related information. Please use the user journey [here](https://docs.corppass.gov.sg/products/myinfo-business/getting-started/user-journey).

4. **Login with Mandatory Face Verification API** - Enhance Singpass Login with an additional face verification step. This is restricted to approved high-risk use cases, such as digital token setup for banking applications. Please refer to the [SFV eligibility guidelines](/docs/products/singpass-face-verification.md) before applying.

{% file src="/files/9O5N1MnsUyfH7LTFwRVC" %}

Once you’ve completed the User Journey, please submit it via the [portal](https://developer.singpass.gov.sg). Your submission will then be routed for approval.


---

# 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/getting-started/user-journey.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.