> 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-portal-sdp/getting-access/obtaining-access-to-the-singpass-developer-portal-sdp.md).
# Obtaining Access to the Singpass Developer Portal (SDP)
This page offers a guide to obtain access and login to SDP
To log in to the [Singpass Developer Portal](https://developer.singpass.gov.sg), your Singpass account must first be authorised via Corppass to act on behalf of your organisation.
**Step 1 — Identify your Corppass Admin**
1. Visit [https://www.corppass.gov.sg](https://www.corppass.gov.sg/)
2. Go to Services → Find your Corppass Admin
3. Authenticate with Singpass
4. Search for your organisation using the Unique Entity Number (UEN)
This will show you who the **Corppass Admin(s)** are within your entity.
**Step 2 — Request Access**
Contact your Corppass Admin and ask them to grant your Singpass account the necessary permissions to access:
* **Singpass Developer Portal**
Once the admin assigns the access rights, you will be able to log in to the Singpass Developer Portal.
---
# 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 dynamically 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-portal-sdp/getting-access/obtaining-access-to-the-singpass-developer-portal-sdp.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
