Unified Provider Launch — Oct 13, 2026
Goes live on October 13, 2026Manage Google & Microsoft mailboxes from one place#
Buy, manage and track your Google Workspace and Microsoft 365 mailboxes together, with no more switching between separate dashboards.One plan for both providers#
Buy and assign Google and Microsoft mailboxes under a single plan.Plans that work interchangeably#
Already have both Google and Microsoft plans? They can now be used interchangeably.One unified view#
See all your mailboxes in one place, regardless of provider.
For API users#
Changes to the Public API#
From October 13, 2026, requests and responses are no longer scoped to a single provider. Your API key, endpoints and versions stay the same. Here's what changes in responses, and what to check in your integration.Example: GET /mailboxes · x-service-provider: GOOGLE#
Today — Only the provider in the header is returned:| Domain | Provider |
|---|
| acme-mail.com | Google |
| acme-send.com | Google |
| acme-outreach.com | (not returned) |
From October 13, 2026 — Both providers, each labelled by serviceProvider:| Domain | Provider |
|---|
| acme-mail.com | Google |
| acme-send.com | Google |
| acme-outreach.com | Microsoft (new) |
What's changing#
Reads return both providers
x-service-provider no longer narrows list responses. Domains, mailboxes and subscriptions come back for Google and Microsoft together.Each resource carries its provider
Read serviceProvider on every item instead of inferring it from your request. Mailboxes always have one.serviceProvider can be null
Subscriptions bought after the upgrade, and domains with no mailbox assigned yet, return serviceProvider: null.Domains aren't tied to a provider when bought
A newly bought domain isn't scoped to Google or Microsoft. It takes the provider of the first mailbox assigned to it, switching from null to GOOGLE or MICROSOFT, so don't cache the value.
What stays the same#
No migration, no new key, nothing to re-provision.Existing domains & mailboxes
Check your integration#
If your code assumes a single provider, check these before October 13, 2026:1.
Handle lists that mix GOOGLE and MICROSOFT items.
2.
Read serviceProvider from each item, not from your request headers.
3.
Allow null for serviceProvider on subscriptions and domains, including in strict types (TypeScript, zod, Pydantic).
4.
Don't treat null as Microsoft. A check like provider === 'GOOGLE' ? … : … sends it down the wrong branch.
Questions about the upgrade? Our team can walk you through what it means for your account or your API integration.
Modified at 2026-10-06 07:32:25