docs: fix Google Workspace shared-domain setup - #248
Merged
Merged
Conversation
📋 View the side-by-side API change reviewThe link expires in 7 days. 🔒 Your API specs are encrypted in CI before they're uploaded. The decryption key stays in this link's URL fragment (after the #), which browsers never send to a server, so oasdiff cannot read your specs. How it works → Posted automatically by the oasdiff GitHub Action. To turn this off (no spec upload, no comment), set |
✨ API Changes# API Changelog n/a vs. n/a
## API Changes
### POST /v0/domains
- added the new optional request property `allow_conflicting_provider`
- added the non-success response with the status `422`
### POST /v0/pods/{pod_id}/domains
- added the new optional request property `allow_conflicting_provider`
- added the non-success response with the status `422`💡 Download |
✨ API Changes# API Changelog n/a vs. n/a
## API Changes
### POST /v0/domains
- added the new optional request property `allow_conflicting_provider`
- added the non-success response with the status `422`
### POST /v0/pods/{pod_id}/domains
- added the new optional request property `allow_conflicting_provider`
- added the non-success response with the status `422`💡 Download |
✨ API Changes# API Changelog n/a vs. n/a
## API Changes
### POST /v0/domains
- added the new optional request property `allow_conflicting_provider`
- added the non-success response with the status `422`
### POST /v0/pods/{pod_id}/domains
- added the new optional request property `allow_conflicting_provider`
- added the non-success response with the status `422`💡 Download |
sidharth0612
approved these changes
Sep 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Google Workspace users following the shared-domain guide hit a 422 during registration because the guide omits
allow_conflicting_provider. Its MX example also incorrectly places the SES feedback endpoint at the root domain.Changes
allow_conflicting_provider: trueand document the existing option in the shared domain-create request, including the 422 response for both organization and pod routes.mail.<domain>, preserve Google's records, and use the regional targets returned by the API.Validation
fern check: 0 errors, 29 warnings.python3 scripts/generate_mcp_tool_catalog.py --check: passed.git diff --check: passed.esbuildwithERR_PNPM_INVALID_WORKSPACE_CONFIGURATION(after resolving its initial workspace-root check), then reports a missingnode-polyfills.cjs. The PR preview workflow is running separately.