Enable email sending for a domain

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Turns on email sending from a domain the app already owns, so your app's email comes from your own address instead of Base44's.

The domain has to be connected to the app first, and ready. A domain you brought yourself must be verified, and one bought through Base44 must have finished propagating. Until then the call fails, and the message says which requirement is missing.

An app sends emails from one domain at a time. If one is already set up, this call is rejected whatever state that domain is in. Disable it first, or use Replace the email domain, which keeps the current domain sending while the new one verifies.

Email isn't live when this returns. The domain still needs DNS records in place, and who publishes them depends on who runs its DNS:

• When Base44 runs the DNS, it writes the records itself and the domain moves toward verification on its own.
• When you run the DNS, publish the records yourself. The domain waits at pending_user_dns_configuration until they resolve.

Either way the records come back in dns_records, so you can pass them to whoever manages the domain's DNS.

Poll List email domains until configuration_status reads active, which is when mail starts sending.

Turning a domain back on after you disabled it skips the DNS and verification steps. It returns to the state it was in, so a domain that was already sending resumes at once.

{
  "domain": "example.com",
  "sender_name": "Nordwind Furniture",
  "from_email": "no-reply@example.com"
}

{
  "domain": "example.com",
  "status": "pending_user_dns_configuration",
  "email_domain_id": "68b1c0d4e7b91d003c45a1f2",
  "external": true,
  "dns_records": [
    {
      "name": "em1234.example.com",
      "status": "pending",
      "ttl": 300,
      "type": "CNAME",
      "value": "u1234567.wl123.sendgrid.net"
    }
  ],
  "provider_id": "godaddy"
}