From 280da801bab4f18ed7fd486bb37e551b50846651 Mon Sep 17 00:00:00 2001 From: Caio Pizzol Date: Mon, 18 May 2026 11:38:47 -0300 Subject: [PATCH] fix(proxy-actions): clarify x-amp-project-id header requires UUID 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. --- src/proxy-actions.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/proxy-actions.mdx b/src/proxy-actions.mdx index b3493416..549e977a 100644 --- a/src/proxy-actions.mdx +++ b/src/proxy-actions.mdx @@ -23,7 +23,7 @@ Please refer to the [Provider Guides](/provider-guides) for the base URL of each Keep the request body and HTTP verb the same, and add these additional headers so Ampersand knows how to deliver the API request: * `x-amp-proxy-version`: this should always be 1 -* `x-amp-project-id`: your Ampersand project ID. You can find it on your project's [General Settings page](https://dashboard.withampersand.com/projects/_/settings) +* `x-amp-project-id`: your Ampersand project UUID, not the project name. You can find it on your project's [General Settings page](https://dashboard.withampersand.com/projects/_/settings). Unlike Platform API paths that accept either project name or UUID, this header requires the UUID. * `x-api-key`: your Ampersand API key, if you don't have one yet, create one in the Ampersand Dashboard's [API Keys page](https://dashboard.withampersand.com/projects/_/api-keys). In order for Ampersand to know which SaaS instance to make the API call against, you'll need to provide either: @@ -40,7 +40,7 @@ Here is an example API call: ```bash curl --location --request PUT 'https://proxy.withampersand.com/services/data/v56.0/sobjects/Account' \ --header 'Content-Type: application/json' \ # Other content types are supported ---header 'x-amp-project-id: my-ampersand-project-id' \ +--header 'x-amp-project-id: ' \ --header 'x-api-key: my-api-key' \ --header 'x-amp-proxy-version: 1' \ --header 'x-amp-integration-name: my-salesforce-integration' \