Domains

Sending domains are the addresses your product sends from. Each domain belongs to a Team (tenant) and must complete DNS-based verification — DKIM, SPF, and MAIL FROM — before it can send. This page documents the REST endpoints for managing domains programmatically.

Base URL and auth

All requests go to the self-hosted instance and use HTTP Bearer auth.

POST /v1/domains HTTP/1.1
Host: mail.everjust.app
Authorization: Bearer us_xxx
Content-Type: application/json

The full base URL is https://mail.everjust.app/api/v1. Rate limiting is disabled on this self-hosted instance, so no 429 throttling applies to domain management.

Endpoints

Create a domain

POST /v1/domains

curl -X POST https://mail.everjust.app/api/v1/domains \
  -H "Authorization: Bearer us_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "send.everjust.app",
    "region": "us-east-1"
  }'

import { UseSend } from "usesend-js";

const usesend = new UseSend("us_xxx", "https://mail.everjust.app/api/v1");

const { data, error } = await usesend.domains.create({
  name: "send.everjust.app",
  region: "us-east-1",
});

from usesend import UseSend

usesend = UseSend("us_xxx", "https://mail.everjust.app/api/v1")

domain = usesend.domains.create({
    "name": "send.everjust.app",
    "region": "us-east-1",
})

The response is a full Domain object, including the dnsRecords array you must publish at your DNS provider.

List domains

GET /v1/domains

Returns an array of every Domain owned by the Team. No query parameters.

curl https://mail.everjust.app/api/v1/domains \
  -H "Authorization: Bearer us_xxx"

const { data, error } = await usesend.domains.list();

domains = usesend.domains.list()

Retrieve a domain

GET /v1/domains/{id}

Fetch a single Domain by its numeric id. Poll this endpoint (or verify) to watch the status and dnsRecords[].status fields change as DNS propagates.

curl https://mail.everjust.app/api/v1/domains/3 \
  -H "Authorization: Bearer us_xxx"

const { data, error } = await usesend.domains.get(3);

domain = usesend.domains.get(3)

Verify a domain

PUT /v1/domains/{id}/verify

Triggers a re-check of the domain's DNS records against SES. Send no body. Call this after you have published the DNS records, and again as needed until status reaches SUCCESS.

curl -X PUT https://mail.everjust.app/api/v1/domains/3/verify \
  -H "Authorization: Bearer us_xxx"

const { data, error } = await usesend.domains.verify(3);

result = usesend.domains.verify(3)

{ "message": "Domain verification started" }

Delete a domain

DELETE /v1/domains/{id}

Removes the domain from the Team. Emails already sent are unaffected, but you can no longer send from the domain.

curl -X DELETE https://mail.everjust.app/api/v1/domains/3 \
  -H "Authorization: Bearer us_xxx"

const { data, error } = await usesend.domains.delete(3);

result = usesend.domains.delete(3)

{ "id": 3, "success": true, "message": "Domain deleted" }

The Domain object

The dnsRecords array

Each entry describes one DNS record you must create at your DNS provider. Publish all of them, then run verify.

{
  "id": 3,
  "name": "send.everjust.app",
  "teamId": 1,
  "status": "PENDING",
  "region": "us-east-1",
  "clickTracking": false,
  "openTracking": false,
  "dkimStatus": "PENDING",
  "spfDetails": "PENDING",
  "dmarcAdded": false,
  "dnsRecords": [
    {
      "type": "TXT",
      "name": "resend._domainkey.send.everjust.app",
      "value": "p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQ...",
      "ttl": "Auto",
      "priority": null,
      "status": "PENDING",
      "recommended": false
    },
    {
      "type": "MX",
      "name": "send.everjust.app",
      "value": "feedback-smtp.us-east-1.amazonses.com",
      "ttl": "Auto",
      "priority": 10,
      "status": "PENDING",
      "recommended": false
    },
    {
      "type": "TXT",
      "name": "send.everjust.app",
      "value": "v=spf1 include:amazonses.com ~all",
      "ttl": "Auto",
      "priority": null,
      "status": "PENDING",
      "recommended": false
    }
  ]
}

Verification lifecycle

A new domain moves through these states:

FAILED means verification could not complete (usually a missing or incorrect record); fix the DNS entry and call verify again. TEMPORARY_FAILURE indicates a transient issue — retry verification later.

Open and click tracking

The openTracking and clickTracking fields appear on the Domain object as read-only booleans over the REST API. There is no public REST endpoint to update tracking — toggle these in the useSend dashboard at mail.everjust.app under the domain's settings.

Errors

Errors use the standard envelope:

{ "error": { "code": "NOT_FOUND", "message": "Domain not found" } }