Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.319 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · api

Update Workspace changedapi/beta/organization/workspaces/update

Nearest release: v2.1.315, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+37added
Lines−27removed
From line 59 where the diff opens
First seen 26 Aug 2026 this site's first read of the page
Recorded edits11to this page, all time

The whole hunk

from line 59, old and new numbered
/
lines
from line 59
5959 Workspace. Setting this field requires CMEK to be enabled for your
6060 organization. When set, data stored for this Workspace is encrypted with the
6161 referenced key. Create key configurations with the External Keys API. On
62 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
63 single-Region key in the same AWS account and Region as the Workspace. On that
64 platform the key is validated against this Workspace when it is attached, so a
65 key-policy problem is reported as an error on this request. This field is write-once:
66 once a key is attached to a Workspace it cannot be detached or replaced. To
67 rotate key material, rotate the underlying key on your cloud KMS; the
68 `external_key_id` stays the same.
62 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
63 organization's own key must be a single-Region key in the same AWS account and
64 Region as the Workspace. On that platform the key is validated against this
65 Workspace when it is attached, so a key-policy problem is reported as an error
66 on this request. This field is write-once: once a key is attached to a Workspace
67 it cannot be detached or replaced. To rotate key material, rotate the underlying
68 key on your cloud KMS; the `external_key_id` stays the same.
6969 
7070- `name: optional string`
7171 
from line 77
7777 
7878 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
7979 
80- `user_profile_id: optional string`
81 
82 ID of a user profile to attach to the Workspace. Every inference request through the Workspace must then name this user profile; the API rejects a request that names none or a different one. Once set, it can't be replaced or removed (sending the same ID again changes nothing); only deleting the user profile clears it. The default Workspace can't have a user profile.
83 
8084## Returns
8185 
8286- `BetaWorkspace object`
from line 105
101105 
102106 - `compartment_id: string`
103107 
104 Identifier for this Workspace's encryption compartment. When you configure a
105 customer-managed encryption key (CMEK) on AWS, reference this value in your
106 KMS key-policy condition so the key is scoped to this compartment. On GCP and
107 Azure, Anthropic enforces the compartment binding automatically; you do not
108 need to reference this value in your key configuration. See the CMEK
109 integration guide for the required key configuration; unless your organization
110 is on Claude Platform on AWS, it includes a separate value used during key
111 validation. On Claude Platform on AWS there is no separate validation value:
112 the key is validated against this Workspace's own value when it is attached, so
113 if your key policy uses the compartment condition, add this value to it before
114 attaching the key.
108 Identifier for this Workspace's encryption compartment. When you configure an
109 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
110 profile, reference this value in your KMS key-policy condition so the key is
111 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
112 binding automatically; you do not need to reference this value in your key
113 configuration. See the CMEK integration guide for the required key
114 configuration; unless your organization is on Claude Platform on AWS, it
115 includes a separate value used during key validation. On Claude Platform on AWS
116 there is no separate validation value: your organization's own key is validated
117 against this Workspace's own value when it is attached, so if its key policy
118 uses the compartment condition, add this value to it before attaching the key.
115119 
116120 - `created_at: string`
117121 
from line 161
157161 Workspace. Setting this field requires CMEK to be enabled for your
158162 organization. When set, data stored for this Workspace is encrypted with the
159163 referenced key. Create key configurations with the External Keys API. On
160 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
161 single-Region key in the same AWS account and Region as the Workspace. On that
162 platform the key is validated against this Workspace when it is attached, so a
163 key-policy problem is reported as an error on this request. This field is write-once:
164 once a key is attached to a Workspace it cannot be detached or replaced. To
165 rotate key material, rotate the underlying key on your cloud KMS; the
166 `external_key_id` stays the same.
164 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
165 organization's own key must be a single-Region key in the same AWS account and
166 Region as the Workspace. On that platform the key is validated against this
167 Workspace when it is attached, so a key-policy problem is reported as an error
168 on this request. This field is write-once: once a key is attached to a Workspace
169 it cannot be detached or replaced. To rotate key material, rotate the underlying
170 key on your cloud KMS; the `external_key_id` stays the same.
167171 
168172 - `name: string`
169173 
from line 177
173177 
174178 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
175179 
180 - `user_profile_id: string or null`
181 
182 ID of the user profile attached to the Workspace, or null if it has none. Every inference request through a Workspace that has a user profile must name that profile.
183 
176184## Example
177185 
178186```bash
from line 194
186194 "tags": {
187195 "env": "prod",
188196 "team": "platform"
189 }
197 },
198 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
190199 }'
191200```
192201 
from line 219
210219 "env": "prod",
211220 "team": "platform"
212221 },
213 "type": "workspace"
222 "type": "workspace",
223 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
214224}
215225```
216226 
Feedback