Nomsa Guide
  • 👋About Nomsa
  • Campaign Guide - General
    • 🚀How to send a campaign?
  • Campaign Guide - Email
    • 📧Email Campaigns - Basics
      • Scheduled Sending
      • Bounced Emails and Halted Campaigns
      • Email Statistics
      • Formatting your Message Template
      • Variable Fields
      • Unique URL Link per Recipient
      • Pasting Content from Microsoft Word
      • Manage your Unsubscriptions
      • Understanding Unsubscriptions
    • 🔐Sending Password-Protected Emails
      • Tutorial
  • Campaign Guide - SMS
    • 📲SMS Campaigns - Basics
    • SMS Onboarding Overview
      • How do I send SMS
  • Campaign Guide - Telegram
    • 🤖Telegram Campaigns - Basics
      • Add Telegram Bot Token in Nomsa
      • Instructions for Recipient Onboarding
      • Use the Bot in the Campaign
      • Telegram Formatting
      • Telegram Bot Statistics
  • Api Guide
    • 📖Overview
      • API Response Formats
      • Bearer Authentication
      • Generate your API Key
      • Rotate your API Key
    • 📨Programmatic Email API
      • Custom From Address
      • Tracking Email Status
      • Send Email API
        • From Name and From Address
        • CC and BCC
        • Recipient Blacklist
        • Email Tagging and Classification
        • Email Body
          • Embedding Images
            • Linked Images
            • Content-ID Images
        • Attachments
        • Rate Limit
      • Get Email by ID API
      • List Emails API
    • 📬Programmatic SMS API
Powered by GitBook
On this page
  • Email Tagging
  • Email Classification
  1. Api Guide
  2. Programmatic Email API
  3. Send Email API

Email Tagging and Classification

PreviousRecipient BlacklistNextEmail Body

Last updated 1 year ago

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 (/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:

{
 "recipient": "bopha@agency.gov.kh",
 "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 (/transactional/email/{id}), the tag field will be returned as part of the JSON object.

In the , 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 .

Email Classification

Our (/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:

{f
 "recipient": "bopha@agency.gov.kh",
 "subject": "Hello there",
 "body": "How are you",
 "classification": "FOR_ACTION"
}

When the API user queries for the email using the (/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 .

📨
email sending API endpoint
email status API endpoint
List Emails API
contact us
email sending API endpoint
email status API endpoint
contact us