Onboard a Product

Create a Team for the product

In the dashboard, create a new Team — one Team per product. The Team is the tenant boundary: its domains, API keys, contacts, campaigns, and analytics are fully isolated from every other product. Name it after the product so it is unambiguous in the Team switcher.

Team creation is a dashboard action; there is no public REST endpoint for it.

Add a sending domain

Use a subdomain dedicated to sending — e.g. send.yourproduct.com — never the product's root domain. This keeps the sending reputation and DNS isolated from the rest of the product's mail and web records.

Add it in the dashboard (Domains → Add) or over the API:

curl -X POST https://mail.everjust.app/api/v1/domains \
  -H "Authorization: Bearer us_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "send.yourproduct.com",
    "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.yourproduct.com",
  region: "us-east-1",
});

from usesend import UseSend

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

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

region is required and must match the deployment's SES region (us-east-1). The response is a Domain object whose numeric id you use in later calls, and whose dnsRecords array holds the records to publish in the next step.

Publish the DNS records useSend shows you

Open the domain in the dashboard (or read dnsRecords from the create response) and publish every record. For send.yourproduct.com you get:

Use the exact name, value, ttl, and priority values that useSend renders — the table above shows the shape, not verbatim strings. DMARC is marked recommended; publish it.

If the domain is in Route 53, script the whole set:

./scripts/add-tenant-dns.sh send.yourproduct.com

Verify the domain

Once DNS has propagated, trigger verification from the dashboard (Verify domain) or over the API:

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

await usesend.domains.verify(42);

usesend.domains.verify(42)

Poll the domain until its status reaches SUCCESS and dkimStatus confirms DKIM is verified — DKIM must reach SUCCESS before SES will accept sends. Propagation can take anywhere from minutes to a few hours depending on the DNS provider's TTL.

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

Create a scoped API key

In Developer settings, create an API key for this product's Team. Keys carry the us_ prefix and are used as an HTTP Bearer token:

Authorization: Bearer us_xxx

Store it in the product's secret manager. API-key creation is dashboard-only — there is no public endpoint for minting keys.

Send a test to the SES simulator

Confirm the whole path end-to-end by sending to the simulator's success address:

curl -X POST https://mail.everjust.app/api/v1/emails \
  -H "Authorization: Bearer us_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "YourProduct <hello@send.yourproduct.com>",
    "to": "success@simulator.amazonses.com",
    "subject": "useSend onboarding test",
    "html": "<p>If this is delivered, the tenant is live.</p>"
  }'

const { data, error } = await usesend.emails.send({
  from: "YourProduct <hello@send.yourproduct.com>",
  to: "success@simulator.amazonses.com",
  subject: "useSend onboarding test",
  html: "<p>If this is delivered, the tenant is live.</p>",
});

result = usesend.emails.send({
    "from_": "YourProduct <hello@send.yourproduct.com>",
    "to": "success@simulator.amazonses.com",
    "subject": "useSend onboarding test",
    "html": "<p>If this is delivered, the tenant is live.</p>",
})

A 200 with {"emailId":"..."} means the send was accepted. Look the email up in the dashboard (or GET /v1/emails/{emailId}) and confirm its status progresses to DELIVERED.