Repository navigation
Conversation
The Admin API, including usage analytics, now works on the US and JP regional endpoints (live for all regional customers since Nov 4). Keys work only on their account's region; other endpoints return 403. - regional-endpoints: replace the Admin Analytics exclusion with an Admin API section. Usage data is currently retrieved from the EU, so responses from regional endpoints can take longer. - admin overview, quickstart, usage data guide: say to use the regional endpoint, linking to the new section without naming hosts - changelog: Nov 4 entry Verified on test accounts: list/create/rename/limit/deactivate keys, usage analytics and custom-tag analytics return 200 on the matching regional endpoint and 403 on the others. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Replace the vague "still retrieved from the EU / use the same paths" bullet with two bullets: requests and responses are unchanged, and usage analytics data is currently retrieved from the EU, so responses can take longer. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- overview: say accounts on a regional endpoint must use it; other endpoints return 403 (was readable as "either endpoint works") - quickstart: Step 4 sends the request to the regional endpoint and links for details instead of restating the EU note; Note trimmed to the action - usage guide: move the regional paragraph after the custom-tags paragraph, align "Currently ... retrieved from the EU", link for timeout guidance - regional endpoints: Admin API becomes a child of API compatibility (same #admin-api anchor) and reads as reference - changelog: split the availability news from the feature definition and state the 403 behavior 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This branch was successfully deployed
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
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.
The Admin API, including usage analytics, now works on the US and JP regional endpoints (live for all regional customers since Nov 4). Keys work only on their account's region; other endpoints return 403.
Verified on test accounts: list/create/rename/limit/deactivate keys, usage analytics and custom-tag analytics return 200 on the matching regional endpoint and 403 on the others.