Latest API and SDK updates. Subscribe via RSS · Discord
Summary
You can now create inboxes on any subdomain of a verified domain without registering each subdomain separately. Enable subdomains_enabled on a domain, publish the single wildcard MX record it returns, and create inboxes on any subdomain on demand. Build agents that spin up addresses like agent@bot.example.com or support@team1.example.com the moment you need them.
What’s new?
New features:
- Subdomains: Opt in per domain with
subdomains_enabled. When enabled, the domain’s verification records include a wildcard MX record (*.<domain>) to publish on the top-level domain. Once it is published and verified, inboxes can be created on any subdomain of that domain.
Changes:
POST /v0/domainsaccepts an optionalsubdomains_enabledflag (defaults tofalse).PATCH /v0/domains/:domain_idnow acceptssubdomains_enabledand applies partial updates: send at least one offeedback_enabledorsubdomains_enabled, and omitted fields are left unchanged. Enabling subdomains on an already-verified domain returns it topendinguntil the new wildcard MX record is published; sending is not interrupted.- Domain responses now include the
subdomains_enabledfield. - Creating an inbox on a subdomain of a domain that does not have subdomains enabled returns a
422error.
Use cases
Build agents that:
- Provision a dedicated inbox per customer or workspace under one verified domain (
support@acme.example.com) - Separate agent traffic onto purpose-named subdomains (
billing.,outreach.,support.) without registering each one - Stand up short-lived inboxes on fresh subdomains for one-off tasks, then tear them down
- Keep all agent addresses under a single domain you verify and manage once
Learn more in the Setting Up Subdomains guide.
