The whole hunk
from line 12, old and new numbered
/
lines
from line 12
1212
1313 - `string`
1414
15 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 38 more`
15 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 41 more`
1616
1717 - `"message-batches-2024-09-24"`
1818
from line 96
9696
9797 - `"ce-user-management-2026-07-13"`
9898
99 - `"mid-conversation-output-config-2026-07-01"`
100
101 - `"thinking-binding-controls-2026-08-01"`
102
103 - `"mid-conversation-system-clear-at-2026-08-21"`
104
99105## Body parameters
100106
101107- `name: string`
from line 149
143149 ID of the customer-managed encryption key (CMEK) configuration to use for this
144150 Workspace. Setting this field requires CMEK to be enabled for your
145151 organization. When set, data stored for this Workspace is encrypted with the
146 referenced key. Create key configurations with the External Keys API. This
147 field is write-once: once a key is attached to a Workspace it cannot be
148 detached or replaced. To rotate key material, rotate the underlying key on
149 your cloud KMS; the `external_key_id` stays the same.
152 referenced key. Create key configurations with the External Keys API. On
153 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
154 single-Region key in the same AWS account and Region as the Workspace. On that
155 platform the key is validated against this Workspace when it is attached, so a
156 key-policy problem is reported as an error on this request. This field is write-once:
157 once a key is attached to a Workspace it cannot be detached or replaced. To
158 rotate key material, rotate the underlying key on your cloud KMS; the
159 `external_key_id` stays the same.
150160
151161- `tags: optional map[string] or null`
152162
from line 182
172182 customer-managed encryption key (CMEK) on AWS, reference this value in your
173183 KMS key-policy condition so the key is scoped to this compartment. On GCP and
174184 Azure, Anthropic enforces the compartment binding automatically; you do not
175 need to reference this value in your key configuration. See the CMEK integration guide for the
176 required key configuration, including the value used during key validation.
185 need to reference this value in your key configuration. See the CMEK
186 integration guide for the required key configuration; unless your organization
187 is on Claude Platform on AWS, it includes a separate value used during key
188 validation. On Claude Platform on AWS there is no separate validation value:
189 the key is validated against this Workspace's own value when it is attached, so
190 if your key policy uses the compartment condition, add this value to it before
191 attaching the key.
177192
178193 - `created_at: string`
179194
from line 225
210225 ID of the customer-managed encryption key (CMEK) configuration to use for this
211226 Workspace. Setting this field requires CMEK to be enabled for your
212227 organization. When set, data stored for this Workspace is encrypted with the
213 referenced key. Create key configurations with the External Keys API. This
214 field is write-once: once a key is attached to a Workspace it cannot be
215 detached or replaced. To rotate key material, rotate the underlying key on
216 your cloud KMS; the `external_key_id` stays the same.
228 referenced key. Create key configurations with the External Keys API. On
229 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
230 single-Region key in the same AWS account and Region as the Workspace. On that
231 platform the key is validated against this Workspace when it is attached, so a
232 key-policy problem is reported as an error on this request. This field is write-once:
233 once a key is attached to a Workspace it cannot be detached or replaced. To
234 rotate key material, rotate the underlying key on your cloud KMS; the
235 `external_key_id` stays the same.
217236
218237 - `name: string`
219238