Provision email sending domains through the API

You can now provision and check an email sending domain through the API instead of only reading the addresses already on one. POST /api/v2/workspaces/{workspace_id}/emails/domains provisions a domain and returns the DKIM, SPF, DMARC and return-path records to add at the registrar, GET /api/v2/emails/domains/{id} reads the stored state back, and POST /api/v2/emails/domains/{id}/verify re-runs the DNS checks (cached for about 10 minutes).

One domain name has two independent jobs, and sending needs both: verified covers email transport (the DNS records above, or a verified SMTP setting), while ownership_verified means the workspace has connected that name in ClickFunnels as a website domain. ready_for_sending is the single flag to poll, and every response carries plain-English next_steps naming whatever is still missing. That is why an address whose domain says verified: true could still refuse to send: pick senders by the address's usable_as_sender field, not by the domain's verified flag.

Agent examples: an agent onboarding a customer can provision the domain, hand the customer the exact registrar records, poll ready_for_sending, and only then create the from-address it will send with, instead of guessing why a broadcast failed at send time.

Resources: Emails::Domain, Emails::Address
Building with an AI agent? Point it at the Emails skill.