> 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/email-tagging-and-classification.md).

# Email Tagging and Classification

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

We have implemented these features to allow you to better keep track of the types of emails that you are sending via our programmatic email API. These features are experimental and we are happy to iterate on them based on user feedback.

## Email Tagging

Our [email sending API endpoint](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api.md) (`/transactional/email/send`) now accepts an optional `tag` field. This field accepts a string of up to 255 characters.

An example JSON payload making use of this `tag` field:

```JSON
{
 "recipient": "recipient@agency.gov.sg",
 "subject": "Hello there",
 "body": "How are you",
 "classification": "FOR_ACTION",
 "tag": "Greetings v2"
}
```

In this example, the `tag` field is wholly defined by the API user. When the API user queries for the email using the [email status API endpoint](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/get-email-by-id-api.md) (`/transactional/email/{id}`), the `tag` field will be returned as part of the JSON object.

In the [List Emails API](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/list-emails-api.md), the API user can query for emails with a specific tag using the `tag` query parameter. For example, `GET /transactional/email?tag=Greetings%20v2` will return all emails with the tag `Greetings v2`.

To make this feature more useful, we are considering generating monthly reports of the different emails based on these user-defined tags. If you have ideas for how this feature might be useful to you, please [contact us](https://go.gov.sg/postman-contact-us).

## Email Classification

Our [email sending API endpoint](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/send-email-api.md) (`/transactional/email/send`) now accepts an optional `classification` field. This fields accepts one of the following enums:

* `URGENT`
* `FOR_ACTION`
* `FOR_INFO`

An example JSON payload making use of this `classification` field:

```JSON
{
 "recipient": "recipient@agency.gov.sg",
 "subject": "Hello there",
 "body": "How are you",
 "classification": "FOR_ACTION"
}
```

When the API user queries for the email using the [email status API endpoint](https://postman-v1.guides.gov.sg/email-api-guide/programmatic-email-api/get-email-by-id-api.md) (`/transactional/email/{id}`), the `classification` field will be returned as part of the JSON object.

We encourage users to make use of this field. To make this feature more useful, we are considering priority sending of emails based on this classification. If you have ideas for how this feature might be useful to you, please [contact us](https://go.gov.sg/postman-contact-us).


---

# 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/email-tagging-and-classification.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.
