Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
One change · api

Update Workspace changed

api/beta/organization/workspaces/update

Nearest release: v2.1.258, published an hour after 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+23added
Lines−10removed
From line 45 where the diff opens
First seen 26 Aug 2026 this site's first read of the page
Recorded edits4to this page, all time

The whole hunk

from line 45, old and new numbered
/
lines
from line 45
4545 ID of the customer-managed encryption key (CMEK) configuration to use for this
4646 Workspace. Setting this field requires CMEK to be enabled for your
4747 organization. When set, data stored for this Workspace is encrypted with the
48 referenced key. Create key configurations with the External Keys API. This
49 field is write-once: once a key is attached to a Workspace it cannot be
50 detached or replaced. To rotate key material, rotate the underlying key on
51 your cloud KMS; the `external_key_id` stays the same.
48 referenced key. Create key configurations with the External Keys API. On
49 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
50 single-Region key in the same AWS account and Region as the Workspace. On that
51 platform the key is validated against this Workspace when it is attached, so a
52 key-policy problem is reported as an error on this request. This field is write-once:
53 once a key is attached to a Workspace it cannot be detached or replaced. To
54 rotate key material, rotate the underlying key on your cloud KMS; the
55 `external_key_id` stays the same.
5256 
5357- `name: optional string`
5458 
from line 84
8084 customer-managed encryption key (CMEK) on AWS, reference this value in your
8185 KMS key-policy condition so the key is scoped to this compartment. On GCP and
8286 Azure, Anthropic enforces the compartment binding automatically; you do not
83 need to reference this value in your key configuration. See the CMEK integration guide for the
84 required key configuration, including the value used during key validation.
87 need to reference this value in your key configuration. See the CMEK
88 integration guide for the required key configuration; unless your organization
89 is on Claude Platform on AWS, it includes a separate value used during key
90 validation. On Claude Platform on AWS there is no separate validation value:
91 the key is validated against this Workspace's own value when it is attached, so
92 if your key policy uses the compartment condition, add this value to it before
93 attaching the key.
8594 
8695 - `created_at: string`
8796 
from line 127
118127 ID of the customer-managed encryption key (CMEK) configuration to use for this
119128 Workspace. Setting this field requires CMEK to be enabled for your
120129 organization. When set, data stored for this Workspace is encrypted with the
121 referenced key. Create key configurations with the External Keys API. This
122 field is write-once: once a key is attached to a Workspace it cannot be
123 detached or replaced. To rotate key material, rotate the underlying key on
124 your cloud KMS; the `external_key_id` stays the same.
130 referenced key. Create key configurations with the External Keys API. On
131 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
132 single-Region key in the same AWS account and Region as the Workspace. On that
133 platform the key is validated against this Workspace when it is attached, so a
134 key-policy problem is reported as an error on this request. This field is write-once:
135 once a key is attached to a Workspace it cannot be detached or replaced. To
136 rotate key material, rotate the underlying key on your cloud KMS; the
137 `external_key_id` stays the same.
125138 
126139 - `name: string`
127140