Configure cloud environments changedcloud-environments
Nearest release: v2.1.319, published 2 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 6 Nov 2026 03:19 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 6 Nov 2026 03:37 UTC.
Upstream edited
Recorded here
Lines+2added
Lines−4removed
From line
116
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits66to this page, all time
The whole hunk
from line 116, old and new numbered
/
from line 116
116116
117117Select **Add secret**, labeled **Add** in admin settings, and fill in the form. Keep the default **Secret type**, **Bearer**, for an API key that travels in a request header, and fill in these fields:
118118
119* **Name**: a label for the secret, such as `Internal billing API`
120119* **Allowed websites**: the API's hosts, such as `api.example.com`. A leading `*.` matches every subdomain
121* **Custom headers**: one row for the header that carries the key. The row starts with `Authorization` as the header's **Name** and `Bearer` as its **Prefix**; paste the key itself as the **Value**. For a header like `X-Api-Key` that takes the bare value, change the name and clear the prefix
120* **Custom headers**: one row for the header that carries the key. The row already has `Authorization` as the **Header name** and `Bearer` as the **Prefix**; paste the key itself as the **Value**. For a header like `X-Api-Key` that takes the bare value, change the name and clear the prefix
122121
123122For an API that authenticates another way, pick a different **Secret type**. The list is the same one [Claude Tag](https://claude.com/docs/claude-tag/overview), the Slack integration for Team and Enterprise plans, offers for [connections](https://claude.com/docs/claude-tag/admins/add-connections).
124123
from line 132
133132If you're on a Team or Enterprise plan and don't hold an [organization admin role](#requirements), the **Add secret** form takes one secret for one host. Select your environment's [**Network secrets** row](#add-a-credential) and then **Add secret**. Fill in these fields and select the form's **Add secret** button:
134133
135134* **Host**: the one host that gets the secret, such as `api.example.com`. The form doesn't accept a `*.` wildcard
136* **Name**: an optional label for the secret
137* **Secret type**: **Token** for a key that travels in a request header, or **Username and password**. For a token, paste the key as the **Value**
135* **Secret type**: **Token** for a key that travels in a request header, or **Username and password**. For a token, paste the key in the **Token** field. For a header other than `Authorization`, such as `X-Api-Key`, change **Header** to its name
138136
139137#### Which requests get the secret
140138
No line in this hunk matches that.