Skip to Content
Uptimeify Docs
Organization sender domain

Sender Domain

Send your organization's emails from your own domain through Uptimeify's mail infrastructure, without running your own SMTP server. Enterprise feature, enabled per organization by Uptimeify. Admin-only.

Your organization's alert, report and status page emails can go out from your own domain (for example alerts@status.example.com) through Uptimeify's mail provider. You add the domain, publish the DNS records the API returns, and once they verify, mail is sent from your address.

This is an Enterprise feature. Until Uptimeify has enabled it for your organization, every endpoint on this page answers 403 with data.code senderDomainNotEnabled.

Which sender is used

  1. Your own SMTP server, when one is configured (Organization SMTP). It always wins.
  2. Your sender domain, while its status is verified.
  3. Otherwise the Uptimeify sender. This includes a domain that loses its verification later: mail keeps arriving, from the Uptimeify sender, until the DNS records are back. Your organization's admins get one email when that happens.

Emails between Uptimeify and your organization (billing, account notices) always come from Uptimeify.

Authentication and permissions

admin role. Closed to API tokens with scopes, customer-bound tokens and agent tokens: use a token without scopes or a session.

BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"

The sender domain object

FieldTypeDescription
domainstringThe sender domain, lower case.
fromEmailstringSender address, always on domain.
fromNamestringSender display name.
replyTostring|nullReply-to address.
statusstringpending (DNS records not verified yet), verified (mail is sent from this domain), failed (was verified, is not anymore).
dnsRecordsarrayThe records to publish: type, hostname, fqdn, content, status (active, pending, failed), purpose, required (needed for verification).
lastCheckedAtstring|nullLast check, ISO 8601 UTC.
verifiedAtstring|nullWhen the domain last became verified.
lastErrorstring|nullWhat the last check reported while not verified.
createdAt, updatedAtstringISO 8601 UTC.

Get the sender domain

GET /api/organization/sender-domain

curl "$BASE_URL/api/organization/sender-domain" -H "Authorization: Bearer $TOKEN"
{
  "domain": "status.example.com",
  "fromEmail": "alerts@status.example.com",
  "fromName": "Example Alerts",
  "replyTo": null,
  "status": "pending",
  "dnsRecords": [
    {
      "type": "CNAME",
      "hostname": "lm1._domainkey",
      "fqdn": "lm1._domainkey.status.example.com",
      "content": "lm1._domainkey.example.lmta.net",
      "status": "pending",
      "purpose": "dkim_primary",
      "required": true
    }
  ],
  "lastCheckedAt": null,
  "verifiedAt": null,
  "lastError": null,
  "createdAt": "2026-11-09T10:00:00.000Z",
  "updatedAt": "2026-11-09T10:00:00.000Z"
}

404 with data.code senderDomainNotConfigured while no domain is set.

Set the sender domain

PUT /api/organization/sender-domain

Adds the domain, or changes it. A new domain starts as pending with fresh dnsRecords; a previous domain is removed. Sending the same domain again changes only the sender fields and keeps the verification.

FieldTypeRequiredDescription
domainstringyesA domain name. A subdomain such as status.example.com is recommended. Lower-cased; a trailing dot is dropped.
fromEmailstringyesSender address. Must be exactly on domain (alerts@status.example.com, not alerts@example.com).
fromNamestringyesDisplay name, 1-200 characters.
replyTostring|nullnoReply-to address; null clears it.

Unknown fields are rejected.

curl -X PUT "$BASE_URL/api/organization/sender-domain" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "domain": "status.example.com", "fromEmail": "alerts@status.example.com", "fromName": "Example Alerts" }'

Answers 200 with the sender domain object.

Check the DNS records now

POST /api/organization/sender-domain/verify

Checks the DNS records right away and answers 200 with the updated sender domain object. Uptimeify also checks every six hours on its own.

curl -X POST "$BASE_URL/api/organization/sender-domain/verify" -H "Authorization: Bearer $TOKEN"

Remove the sender domain

DELETE /api/organization/sender-domain

Removes the domain. Mail goes out from the Uptimeify sender again right away. Answers 204 without a body; a second call answers 404 senderDomainNotConfigured.

curl -X DELETE "$BASE_URL/api/organization/sender-domain" -H "Authorization: Bearer $TOKEN"

Common errors

  • 400 invalidRequestBody: not a domain name, fromEmail not on domain, or an unknown field (data.issues names the field)
  • 400 senderDomainReserved: an Uptimeify domain or one of its subdomains
  • 403 forbidden: not an admin
  • 403 senderDomainNotEnabled: the feature is not enabled for your organization
  • 404 senderDomainNotConfigured: no sender domain set (GET, verify, DELETE)
  • 409 senderDomainTaken: the domain is used by another organization or already registered with the mail provider
  • 502 senderDomainProviderError: the mail provider did not accept the request; try again later
  • 503 senderDomainUnavailable: sender domains are temporarily unavailable

On this page