This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation.
Before sending a customer to checkout for Business Email, you can confirm that their account can purchase it for the domain, and find out how many seats they can buy. This avoids a checkout that fails later, for example because the domain already has a Business Email package.
To check whether an account can purchase Business Email for a domain:
domainName and the Business Email product type ID in productTypeId.result.eligible object is returned, the account can purchase Business Email for the domain. Use result.eligible.seats as the maximum number of seats to offer at checkout.result.notEligible is returned instead, read result.notEligible.reasons and show the customer why they can't purchase Business Email for the domain. For example, domainNotOwnedByUser means the domain belongs to a different account.If your app shows an account's Business Email in its own interface, you can list the mailboxes on a domain and how much of the Google Workspace's storage they use.
To show a Google Workspace's users and storage usage:
domainName. Show each user's primaryEmail and name, and use admin to mark the administrators.googleWorkspacePremiumId.usedMb and quotaMb are returned, show the storage used out of the pooled quota, and use asOfDate to show when the numbers are from. If they aren't returned, show that storage usage isn't available yet.After a customer purchases Business Email, the Google Workspace needs an administrator before its mailboxes can be used. If your app handles the purchase, it can also collect the administrator's details and complete the setup.
To set up the first administrator after a Business Email purchase:
googleWorkspacePremiumId, along with the details you collected. Save the returned primaryEmail.googleWorkspacePremiumId, and confirm the administrator's primaryEmail appears in users.Last updated: 6 October 2026