> For the complete documentation index, see [llms.txt](https://postman-v2.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postman-v2.guides.gov.sg/legacy-integrations/what-are-legacy-integrations.md).

# What are legacy integrations

{% hint style="warning" %}
Please note that the Postman Team will not be actively supporting these integrations. These integrations were created to assist agencies during the transition of the gov.sg sender id mandate.\
\
All agencies should migrate these legacy systems to use Postman to send SMSes via our UI or APIs.
{% endhint %}

The Postman Team created the following integrations to support agencies with legacy systems:

* **SFTP** - agencies who had legacy systems which were unable to make direct API calls
* **Postman NRIC** - agencies who were dependent on Singpass Notify feature

Given that the team is no longer onboarding any new users and these integrations are meant to be decommissioned, the guides for this section will not be available.

Should you require any assistance please reference this page [FAQs (SFTP, Postman NRIC)](/legacy-integrations/faqs-sftp-postman-nric.md) as the team will not be providing active support.


---

# 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://postman-v2.guides.gov.sg/legacy-integrations/what-are-legacy-integrations.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.