Create and manage email sender addresses

Sender addresses are now writable. POST /api/v2/workspaces/:workspace_id/emails/addresses adds a from-address, PATCH /api/v2/emails/addresses/:id updates one, and DELETE /api/v2/emails/addresses/:id retires one. Pair it with the sending-domain endpoints: provision the domain, then pass its id as emails_domain_id on the address. Adding a sender no longer means handing your user back to the ClickFunnels dashboard mid-onboarding, which was the single biggest reason partner email batches failed with "sender not verified".

Pick senders by the address's own usable_as_sender field, not by its domain's verified flag, because the two answer different questions: a verified domain still cannot send from an address the workspace has not made usable. Every address also carries a nested emails_domain with per-record verification booleans, so you can tell a sender that was never set up from one whose DNS lapsed, and filter[verified]=true (or false) narrows the list to one side of that line. filter[email_address] looks a single address up exactly. Two things worth knowing: is_workspace_default: true alongside usable_as_sender: false is expected once the workspace has a usable sender of its own, and DELETE retires an address rather than erasing it, so a retired address disappears from the list and returns 404 afterwards.

Agent examples: onboard a customer end to end, provisioning the domain, adding their from-address, and only sending once it reports usable · re-check a stored sender before a batch and surface the exact DNS record that lapsed.

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