> 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/send-email-api/recipient-blacklist.md).

# Recipient Blacklist

{% 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 %}

## Purpose

We keep a blacklist of email addresses to whom our system will not send emails. Typically, these email addresses are added to the blacklist after a delivery attempt has resulted in a hard bounce, (e.g. the email address does not exist).

Without a blacklist, our system would continue to attempt to send emails to these addresses, which would result in a poor reputation for our system and adversely impact the deliverability of emails to other recipients.

For more information on email deliverability, you can visit [AWS SES's documentation](https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-deliverability.html).

## Is my recipient on the blacklist?

Currently, we do not provide a way to check if a recipient is on the blacklist prior to sending out an email.

However, there are two ways you will be informed if a recipient is on the blacklist:

1. In our current setup, during your API call to our system, we will check if the recipient is on the blacklist. If the recipient is on the blacklist, we will return an error message indicating that the recipient is on the blacklist. However, to scale our system, we plan to change this behavior in the future, so we advise against relying on this behavior.
2. You can query an email by its ID using this [API endpoint](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/get-email-by-id-api.md). If the email was not sent because the recipient was on the blacklist, this will be indicated in the `errorCode` field of the response.

## How do I remove a recipient from the blacklist?

There are some instances where a blacklisted recipient may be a valid recipient. For example, if a recipient's email address was blacklisted because it did not exist, but the recipient has since created an email address with the same email address, then the recipient should be removed from the blacklist.

In this case, you should [contact us](https://go.gov.sg/postman-contact-us) to remove the recipient from the blacklist.


---

# 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/send-email-api/recipient-blacklist.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.
