fix(proxy-actions): clarify x-amp-project-id header requires UUID#613
Open
caiopizzol wants to merge 1 commit into
Open
fix(proxy-actions): clarify x-amp-project-id header requires UUID#613caiopizzol wants to merge 1 commit into
caiopizzol wants to merge 1 commit into
Conversation
The x-amp-project-id header must be the project UUID; using the project name returns HTTP 403 from the proxy server. Other Platform API paths accept either project name or UUID, which made this ambiguity easy to hit. Verified while exercising an Anthropic proxy integration: project name 'drift-check' returned 403 'user or API key is not authorized'; the same request with the project UUID returned 200 with the expected response body.
Contributor
Author
|
@laurenzlong I verified again with a temporary Anthropic proxy installation: UUID in I think this docs change is a workaround for the current behavior, not the ideal product contract. The API-level fix should be for proxy to accept the same project UUID-or-name semantics used by Platform/read/write APIs, or otherwise make the UUID-only requirement explicit in the proxy API contract. Until that API fix lands, this docs update prevents users from following an example that fails. |
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
1 participant
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.
Description
proxy-actions.mdxdocumentsx-amp-project-idas "your Ampersand project ID" without distinguishing project name from project UUID. The proxy server actually requires the UUID; the project name (which works on Platform API paths like/v1/projects/{projectIdOrName}/...) returns HTTP 403 at the proxy.This PR is a 2-line wording fix and an example-placeholder update:
my-ampersand-project-idto<PROJECT_UUID>so the example doesn't suggest a plain identifier is acceptable.Verified: while exercising an Anthropic proxy integration,
x-amp-project-id: drift-check(project name) returned 403"Ampersand user or API key is not authorized to access this resource"; the identical request withx-amp-project-id: <UUID>returned 200 with the expected response body.Screenshot
Not applicable. Pure wording clarification in
proxy-actions.mdx; no provider-guide content or behavior changes.