> For the complete documentation index, see [llms.txt](https://postman-v1.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-v1.guides.gov.sg/email-api-guide/programmatic-email-api/getting-started.md).

# Getting Started

This page gives you an overview of what to expect when onboarding to Postman Programmatic Email API. Onboarding is mostly self-service, with one exception listed below.

{% hint style="warning" %}
**Updated Nov 2026: The Postman Legacy Team will not be providing support for our email API until further notice.**

**Set-up is fully self-service:** Our endpoints remain open, so you may continue to integrate with them if it is sufficient for your use case.

* However, if you experience any issues, we will not be able to provide any support due to limited resources.
* Onboarding to custom from-email addresses and attachments for API is not available.
  {% endhint %}

If you’re unsure if Postman Programmatic Email API is a good fit, get started by reading the following pages:

* If you're an existing AMR user, you can check out this [comparison with AMR](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/comparison-with-amr.md)
* Learn more about the relevant [IM8 Policies](https://postman-v1.guides.gov.sg/email-api-guide/overview/im8-policies.md)
* Find out how to [connect your Intranet application](https://postman-v1.guides.gov.sg/email-api-guide/overview/connecting-your-intranet-application.md) to our API

## Ready to onboard?

Here are the following steps to take note to help you onboard more smoothly.

### **Step 1: Decide on a sender name and from address**

You can configure your from address to be either:

* The default from address: `info@mail.postman.gov.sg`
* A custom from address (e.g. `hello@agency.gov.sg`)

This decision will determine if you require our team's support to configure a custom from address. More info on this can be found [here](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/custom-from-address.md).

### **Step 2: Understand what content you will be sending**

To ensure that your content can be sent successfully, you should read these pages ahead of time.

* [Are you sending any attachments?](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api/attachments.md)
* [Are you sending images?](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api/email-body/embedding-images.md)
* [Is the default send rate of 10 message/s sufficient for your use case?](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api/rate-limit.md)

### **Step 3: If you want to send the emails from your own custom sender email, contact Postman team** [**here**](https://go.gov.sg/postmanp-api-wogict)

This step is optional, and only needed if you wish to set up a custom from address in [step 1](#step-1-decide-on-a-sender-name-and-from-email-address).

Setting up custom sender email typically takes agencies up to 2 weeks to complete so make sure you add buffer time for this step. You may refer to [this page](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/custom-from-address.md) for more details.

### **Step 4: Generate API Key on Postman.gov.sg**

Log in to Postman.gov.sg using the sender email address identified in [**Step 1**](#step-1-decide-on-a-sender-name-and-from-email-address) and generate the API Key. This API key will be used to authenticate your requests. You may follow the steps outlined [here](https://postman-v1.guides.gov.sg/email-api-guide/api-key-management/generate-your-api-key.md).

{% hint style="info" %}
If you wish to use a [custom from address](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/custom-from-address.md), please note that the email address with which you use to log into Postman must be the same as the address from which you wish to send emails.
{% endhint %}

### **Step 5: Start sending your test emails**

Refer to the [steps here](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api.md) on how you can start sending your first email. Note the specific instructions on the [email body](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api/email-body.md), [attachments](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api/attachments.md) and [email tagging and classification](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api/email-tagging-and-classification.md).

As you integrate with the API:

* Find out more about the [status codes and responses you may encounter](https://postman-v1.guides.gov.sg/email-api-guide/overview/api-response-formats.md)
* Understand [the various email statuses and error codes](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/tracking-email-status.md) you may encounter

### **Step 6: Tell us about your experience**

We always strive to improve your user experience and it would mean a lot to us if you could take a few minutes to let us know how your experience was by filling in this [form](https://go.gov.sg/postman-api-feedback).


---

# 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-v1.guides.gov.sg/email-api-guide/programmatic-email-api/getting-started.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.
