Misar Docs
MisarMailMisar.BlogMisarReachMisarPostMisar.DevMisar PlatformMisar IdentityMisar Posts API
Api Reference

Email Aliases

Create and manage from-address sending identities with per-alias SMTP routing

An alias is a verified from-address identity used when sending email. Each alias maps a display name and email address to an SMTP pool (IP group). You can have multiple aliases — for example, noreply@, support@, and marketing@ — each routed through different IP pools for deliverability isolation.

Auth scope: aliases

Endpoints

MethodPathDescription
GET/api/v1/aliasesList sending aliases
POST/api/v1/aliasesCreate an alias
GET/api/v1/aliases/:idGet a single alias
PATCH/api/v1/aliases/:idUpdate an alias
DELETE/api/v1/aliases/:idRemove an alias

List sending aliases

GET/mail/v1/aliases

List all aliases for the authenticated account.

Response fields

successboolean

true when the request succeeded.

aliasesarray

Sending aliases. Each includes id, email, name, is_default, is_verified, ip_pool, and created_at.

curl https://api.misar.io/mail/v1/aliases \
  -H "Authorization: Bearer msk_YOUR_API_KEY"
{
  "success": true,
  "aliases": [
    {
      "id":          "ali_abc123",
      "email":       "[email protected]",
      "name":        "Your Company",
      "is_default":  true,
      "is_verified": true,
      "ip_pool":     "marketing",
      "created_at":  "2026-01-20T10:00:00Z"
    }
  ]
}

Create an alias

POST/mail/v1/aliases

Create a new sending alias. The alias email must be on a verified custom domain or be a connected IMAP account.

Request body

emailstringbodyrequired

From address — must be on a verified domain.

namestringbody

Display name shown to recipients.

is_defaultbooleanbody

Set as default from-address (only one allowed).

ip_poolstringbody

SMTP IP pool: transactional, marketing, or newsletter.

Response fields

successboolean

true when the alias was created.

aliasobject

The created alias, including id, email, name, is_default, is_verified, and ip_pool.

curl -X POST https://api.misar.io/mail/v1/aliases \
  -H "Authorization: Bearer msk_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email":      "[email protected]",
    "name":       "Your Company Marketing",
    "is_default": false,
    "ip_pool":    "marketing"
  }'
{
  "success": true,
  "alias": {
    "id":          "ali_xyz789",
    "email":       "[email protected]",
    "name":        "Your Company Marketing",
    "is_default":  false,
    "is_verified": false,
    "ip_pool":     "marketing"
  }
}

Each alias requires email verification before it can be used for sending. A verification email is sent automatically on alias creation. is_verified becomes true after the recipient clicks the link.

Update an alias

PATCH/mail/v1/aliases/:id

Update an alias. Only name, is_default, and ip_pool can be changed after creation.

Path parameters

idstringpathrequired

ID of the alias to update.

Request body

namestringbody

Display name shown to recipients.

is_defaultbooleanbody

Set as default from-address (only one allowed).

ip_poolstringbody

SMTP IP pool: transactional, marketing, or newsletter.

Response fields

successboolean

true when the alias was updated.

aliasobject

The updated alias.

curl -X PATCH https://api.misar.io/mail/v1/aliases/ali_abc123 \
  -H "Authorization: Bearer msk_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "is_default": true, "ip_pool": "transactional" }'
{
  "success": true,
  "alias": {
    "id":         "ali_abc123",
    "email":      "[email protected]",
    "is_default": true,
    "ip_pool":    "transactional"
  }
}

Remove an alias

DELETE/mail/v1/aliases/:id

Remove an alias. Cannot delete the default alias while active campaigns reference it.

Path parameters

idstringpathrequired

ID of the alias to remove.

Response fields

successboolean

true when the alias was removed.

curl -X DELETE https://api.misar.io/mail/v1/aliases/ali_xyz789 \
  -H "Authorization: Bearer msk_YOUR_API_KEY"
{ "success": true }

Errors

  • 404 — Alias not found
  • 409 — Alias is referenced by active campaigns — reassign first
  • 403 — Cannot delete the only remaining verified alias

IP Pool Options

PoolBest For
transactionalReceipts, password resets, notifications
marketingNewsletters, promotional campaigns
newsletterSubscription digests, content updates

Keeping transactional and marketing sends on separate IP pools protects your transactional deliverability if a marketing campaign generates complaints.