> 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/testing/myinfo-test-personas.md).

# Myinfo Test Personas

We provide a set of Myinfo test personas with diverse attributes and metadata to help you simulate different user profiles when testing your Myinfo integration.

These test personas are intended solely for Myinfo data retrieval and verification testing.

### ⚠️ Important Usage Notes

* **Do not** use these test personas for **Singpass Login** applications.

  These accounts are not meant to be used to test Singpass Login flows.If you need to populate email addresses or mobile numbers to your [staging accounts](/docs/singpass-developer-portal-sdp/app-management/create-staging-test-account.md) for Login flow testing, please use the following form: <https://go.gov.sg/sp-test-acc>
* Test persona details may change over time.

  The profile data associated with these personas is valid only at the time of testing. We may update, modify, or refresh persona attributes at any time without prior notice.
* Do not hardcode values.

  Your integration should not rely on fixed persona attributes (e.g. names, emails, addresses) and should handle changes gracefully.

## Singpass Login Credentials

*(For Myinfo testing only)*

> Username: \[UINFIN reflected in first column of file]\
> Password: `Userinfo@2024`

> These credentials are provided to support Myinfo test flows only and should not be used for production or Login app validation.

Download the full list of test personas below:

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

Note: We updated the test profiles to reflect latest CPF transactions dates.


---

# 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/testing/myinfo-test-personas.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.