Create Workspace changedapi/beta/organization/workspaces/create
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+39added
Lines−27removed
From line
131
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits18to this page, all time
The whole hunk
from line 131, old and new numbered
/
from line 131
131131
132132 - `"analytics-usage-cost-2026-08-24"`
133133
134 - `"experimental-claude-tag-2026-10-21"`
135
134136## Body parameters
135137
136138- `name: string`
from line 181
179181 Workspace. Setting this field requires CMEK to be enabled for your
180182 organization. When set, data stored for this Workspace is encrypted with the
181183 referenced key. Create key configurations with the External Keys API. On
182 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
183 single-Region key in the same AWS account and Region as the Workspace. On that
184 platform the key is validated against this Workspace when it is attached, so a
185 key-policy problem is reported as an error on this request. This field is write-once:
186 once a key is attached to a Workspace it cannot be detached or replaced. To
187 rotate key material, rotate the underlying key on your cloud KMS; the
188 `external_key_id` stays the same.
184 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
185 organization's own key must be a single-Region key in the same AWS account and
186 Region as the Workspace. On that platform the key is validated against this
187 Workspace when it is attached, so a key-policy problem is reported as an error
188 on this request. This field is write-once: once a key is attached to a Workspace
189 it cannot be detached or replaced. To rotate key material, rotate the underlying
190 key on your cloud KMS; the `external_key_id` stays the same.
189191
190192- `tags: optional map[string] or null`
191193
192194 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
193195
196- `user_profile_id: optional string or null`
197
198 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. The user profile can't be replaced or removed later; only deleting the user profile clears it.
199
194200## Returns
195201
196202- `BetaWorkspace object`
from line 221
215221
216222 - `compartment_id: string`
217223
218 Identifier for this Workspace's encryption compartment. When you configure a
219 customer-managed encryption key (CMEK) on AWS, reference this value in your
220 KMS key-policy condition so the key is scoped to this compartment. On GCP and
221 Azure, Anthropic enforces the compartment binding automatically; you do not
222 need to reference this value in your key configuration. See the CMEK
223 integration guide for the required key configuration; unless your organization
224 is on Claude Platform on AWS, it includes a separate value used during key
225 validation. On Claude Platform on AWS there is no separate validation value:
226 the key is validated against this Workspace's own value when it is attached, so
227 if your key policy uses the compartment condition, add this value to it before
228 attaching the key.
224 Identifier for this Workspace's encryption compartment. When you configure an
225 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
226 profile, reference this value in your KMS key-policy condition so the key is
227 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
228 binding automatically; you do not need to reference this value in your key
229 configuration. See the CMEK integration guide for the required key
230 configuration; unless your organization is on Claude Platform on AWS, it
231 includes a separate value used during key validation. On Claude Platform on AWS
232 there is no separate validation value: your organization's own key is validated
233 against this Workspace's own value when it is attached, so if its key policy
234 uses the compartment condition, add this value to it before attaching the key.
229235
230236 - `created_at: string`
231237
from line 277
271277 Workspace. Setting this field requires CMEK to be enabled for your
272278 organization. When set, data stored for this Workspace is encrypted with the
273279 referenced key. Create key configurations with the External Keys API. On
274 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
275 single-Region key in the same AWS account and Region as the Workspace. On that
276 platform the key is validated against this Workspace when it is attached, so a
277 key-policy problem is reported as an error on this request. This field is write-once:
278 once a key is attached to a Workspace it cannot be detached or replaced. To
279 rotate key material, rotate the underlying key on your cloud KMS; the
280 `external_key_id` stays the same.
280 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
281 organization's own key must be a single-Region key in the same AWS account and
282 Region as the Workspace. On that platform the key is validated against this
283 Workspace when it is attached, so a key-policy problem is reported as an error
284 on this request. This field is write-once: once a key is attached to a Workspace
285 it cannot be detached or replaced. To rotate key material, rotate the underlying
286 key on your cloud KMS; the `external_key_id` stays the same.
281287
282288 - `name: string`
283289
from line 293
287293
288294 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
289295
296 - `user_profile_id: string or null`
297
298 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.
299
290300## Example
291301
292302```bash
from line 311
301311 "tags": {
302312 "env": "prod",
303313 "team": "platform"
304 }
314 },
315 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
305316 }'
306317```
307318
from line 336
325336 "env": "prod",
326337 "team": "platform"
327338 },
328 "type": "workspace"
339 "type": "workspace",
340 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
329341}
330342```
331343
No line in this hunk matches that.