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

Get Workspace changedapi/beta/organization/workspaces/retrieve

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+24added
Lines−19removed
From line 47 where the diff opens
First seen 26 Aug 2026 this site's first read of the page
Recorded edits9to this page, all time

The whole hunk

from line 47, old and new numbered
/
lines
from line 47
4747 
4848 - `compartment_id: string`
4949 
50 Identifier for this Workspace's encryption compartment. When you configure a
51 customer-managed encryption key (CMEK) on AWS, reference this value in your
52 KMS key-policy condition so the key is scoped to this compartment. On GCP and
53 Azure, Anthropic enforces the compartment binding automatically; you do not
54 need to reference this value in your key configuration. See the CMEK
55 integration guide for the required key configuration; unless your organization
56 is on Claude Platform on AWS, it includes a separate value used during key
57 validation. On Claude Platform on AWS there is no separate validation value:
58 the key is validated against this Workspace's own value when it is attached, so
59 if your key policy uses the compartment condition, add this value to it before
60 attaching the key.
50 Identifier for this Workspace's encryption compartment. When you configure an
51 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
52 profile, reference this value in your KMS key-policy condition so the key is
53 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
54 binding automatically; you do not need to reference this value in your key
55 configuration. See the CMEK integration guide for the required key
56 configuration; unless your organization is on Claude Platform on AWS, it
57 includes a separate value used during key validation. On Claude Platform on AWS
58 there is no separate validation value: your organization's own key is validated
59 against this Workspace's own value when it is attached, so if its key policy
60 uses the compartment condition, add this value to it before attaching the key.
6161 
6262 - `created_at: string`
6363 
from line 103
103103 Workspace. Setting this field requires CMEK to be enabled for your
104104 organization. When set, data stored for this Workspace is encrypted with the
105105 referenced key. Create key configurations with the External Keys API. On
106 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
107 single-Region key in the same AWS account and Region as the Workspace. On that
108 platform the key is validated against this Workspace when it is attached, so a
109 key-policy problem is reported as an error on this request. This field is write-once:
110 once a key is attached to a Workspace it cannot be detached or replaced. To
111 rotate key material, rotate the underlying key on your cloud KMS; the
112 `external_key_id` stays the same.
106 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
107 organization's own key must be a single-Region key in the same AWS account and
108 Region as the Workspace. On that platform the key is validated against this
109 Workspace when it is attached, so a key-policy problem is reported as an error
110 on this request. This field is write-once: once a key is attached to a Workspace
111 it cannot be detached or replaced. To rotate key material, rotate the underlying
112 key on your cloud KMS; the `external_key_id` stays the same.
113113 
114114 - `name: string`
115115 
from line 119
119119 
120120 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
121121 
122 - `user_profile_id: string or null`
123 
124 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.
125 
122126## Example
123127 
124128```bash
from line 151
147151 "env": "prod",
148152 "team": "platform"
149153 },
150 "type": "workspace"
154 "type": "workspace",
155 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
151156}
152157```
153158 
Feedback