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

List Workspaces changedapi/beta/organization/workspaces/list

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 71 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 71, old and new numbered
/
lines
from line 71
7171 
7272 - `compartment_id: string`
7373 
74 Identifier for this Workspace's encryption compartment. When you configure a
75 customer-managed encryption key (CMEK) on AWS, reference this value in your
76 KMS key-policy condition so the key is scoped to this compartment. On GCP and
77 Azure, Anthropic enforces the compartment binding automatically; you do not
78 need to reference this value in your key configuration. See the CMEK
79 integration guide for the required key configuration; unless your organization
80 is on Claude Platform on AWS, it includes a separate value used during key
81 validation. On Claude Platform on AWS there is no separate validation value:
82 the key is validated against this Workspace's own value when it is attached, so
83 if your key policy uses the compartment condition, add this value to it before
84 attaching the key.
74 Identifier for this Workspace's encryption compartment. When you configure an
75 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
76 profile, reference this value in your KMS key-policy condition so the key is
77 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
78 binding automatically; you do not need to reference this value in your key
79 configuration. See the CMEK integration guide for the required key
80 configuration; unless your organization is on Claude Platform on AWS, it
81 includes a separate value used during key validation. On Claude Platform on AWS
82 there is no separate validation value: your organization's own key is validated
83 against this Workspace's own value when it is attached, so if its key policy
84 uses the compartment condition, add this value to it before attaching the key.
8585 
8686 - `created_at: string`
8787 
from line 127
127127 Workspace. Setting this field requires CMEK to be enabled for your
128128 organization. When set, data stored for this Workspace is encrypted with the
129129 referenced key. Create key configurations with the External Keys API. On
130 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
131 single-Region key in the same AWS account and Region as the Workspace. On that
132 platform the key is validated against this Workspace when it is attached, so a
133 key-policy problem is reported as an error on this request. This field is write-once:
134 once a key is attached to a Workspace it cannot be detached or replaced. To
135 rotate key material, rotate the underlying key on your cloud KMS; the
136 `external_key_id` stays the same.
130 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
131 organization's own key must be a single-Region key in the same AWS account and
132 Region as the Workspace. On that platform the key is validated against this
133 Workspace when it is attached, so a key-policy problem is reported as an error
134 on this request. This field is write-once: once a key is attached to a Workspace
135 it cannot be detached or replaced. To rotate key material, rotate the underlying
136 key on your cloud KMS; the `external_key_id` stays the same.
137137 
138138 - `name: string`
139139 
from line 143
143143 
144144 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
145145 
146 - `user_profile_id: string or null`
147 
148 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.
149 
146150- `first_id: string or null`
147151 
148152 First ID in the `data` list. Can be used as the `before_id` for the previous page.
from line 189
185189 "env": "prod",
186190 "team": "platform"
187191 },
188 "type": "workspace"
192 "type": "workspace",
193 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
189194 }
190195 ],
191196 "first_id": "first_id",
Feedback