Workspaces changedapi/beta/organization/workspaces
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+186added
Lines−135removed
From line
73
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits23to this page, all time
The whole hunk
from line 73, old and new numbered
/
from line 73
7373
7474 - `compartment_id: string`
7575
76 Identifier for this Workspace's encryption compartment. When you configure a
77 customer-managed encryption key (CMEK) on AWS, reference this value in your
78 KMS key-policy condition so the key is scoped to this compartment. On GCP and
79 Azure, Anthropic enforces the compartment binding automatically; you do not
80 need to reference this value in your key configuration. See the CMEK
81 integration guide for the required key configuration; unless your organization
82 is on Claude Platform on AWS, it includes a separate value used during key
83 validation. On Claude Platform on AWS there is no separate validation value:
84 the key is validated against this Workspace's own value when it is attached, so
85 if your key policy uses the compartment condition, add this value to it before
86 attaching the key.
76 Identifier for this Workspace's encryption compartment. When you configure an
77 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
78 profile, reference this value in your KMS key-policy condition so the key is
79 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
80 binding automatically; you do not need to reference this value in your key
81 configuration. See the CMEK integration guide for the required key
82 configuration; unless your organization is on Claude Platform on AWS, it
83 includes a separate value used during key validation. On Claude Platform on AWS
84 there is no separate validation value: your organization's own key is validated
85 against this Workspace's own value when it is attached, so if its key policy
86 uses the compartment condition, add this value to it before attaching the key.
8787
8888 - `created_at: string`
8989
from line 129
129129 Workspace. Setting this field requires CMEK to be enabled for your
130130 organization. When set, data stored for this Workspace is encrypted with the
131131 referenced key. Create key configurations with the External Keys API. On
132 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
133 single-Region key in the same AWS account and Region as the Workspace. On that
134 platform the key is validated against this Workspace when it is attached, so a
135 key-policy problem is reported as an error on this request. This field is write-once:
136 once a key is attached to a Workspace it cannot be detached or replaced. To
137 rotate key material, rotate the underlying key on your cloud KMS; the
138 `external_key_id` stays the same.
132 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
133 organization's own key must be a single-Region key in the same AWS account and
134 Region as the Workspace. On that platform the key is validated against this
135 Workspace when it is attached, so a key-policy problem is reported as an error
136 on this request. This field is write-once: once a key is attached to a Workspace
137 it cannot be detached or replaced. To rotate key material, rotate the underlying
138 key on your cloud KMS; the `external_key_id` stays the same.
139139
140140 - `name: string`
141141
from line 145
145145
146146 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
147147
148 - `user_profile_id: string or null`
149
150 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.
151
148152- `first_id: string or null`
149153
150154 First ID in the `data` list. Can be used as the `before_id` for the previous page.
from line 191
187191 "env": "prod",
188192 "team": "platform"
189193 },
190 "type": "workspace"
194 "type": "workspace",
195 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
191196 }
192197 ],
193198 "first_id": "first_id",
from line 329
324329
325330 - `"analytics-usage-cost-2026-08-24"`
326331
332 - `"experimental-claude-tag-2026-10-21"`
333
327334### Body parameters
328335
329336- `name: string`
from line 379
372379 Workspace. Setting this field requires CMEK to be enabled for your
373380 organization. When set, data stored for this Workspace is encrypted with the
374381 referenced key. Create key configurations with the External Keys API. On
375 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
376 single-Region key in the same AWS account and Region as the Workspace. On that
377 platform the key is validated against this Workspace when it is attached, so a
378 key-policy problem is reported as an error on this request. This field is write-once:
379 once a key is attached to a Workspace it cannot be detached or replaced. To
380 rotate key material, rotate the underlying key on your cloud KMS; the
381 `external_key_id` stays the same.
382 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
383 organization's own key must be a single-Region key in the same AWS account and
384 Region as the Workspace. On that platform the key is validated against this
385 Workspace when it is attached, so a key-policy problem is reported as an error
386 on this request. This field is write-once: once a key is attached to a Workspace
387 it cannot be detached or replaced. To rotate key material, rotate the underlying
388 key on your cloud KMS; the `external_key_id` stays the same.
382389
383390- `tags: optional map[string] or null`
384391
385392 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
386393
394- `user_profile_id: optional string or null`
395
396 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.
397
387398### Returns
388399
389400- `BetaWorkspace object`
from line 419
408419
409420 - `compartment_id: string`
410421
411 Identifier for this Workspace's encryption compartment. When you configure a
412 customer-managed encryption key (CMEK) on AWS, reference this value in your
413 KMS key-policy condition so the key is scoped to this compartment. On GCP and
414 Azure, Anthropic enforces the compartment binding automatically; you do not
415 need to reference this value in your key configuration. See the CMEK
416 integration guide for the required key configuration; unless your organization
417 is on Claude Platform on AWS, it includes a separate value used during key
418 validation. On Claude Platform on AWS there is no separate validation value:
419 the key is validated against this Workspace's own value when it is attached, so
420 if your key policy uses the compartment condition, add this value to it before
421 attaching the key.
422 Identifier for this Workspace's encryption compartment. When you configure an
423 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
424 profile, reference this value in your KMS key-policy condition so the key is
425 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
426 binding automatically; you do not need to reference this value in your key
427 configuration. See the CMEK integration guide for the required key
428 configuration; unless your organization is on Claude Platform on AWS, it
429 includes a separate value used during key validation. On Claude Platform on AWS
430 there is no separate validation value: your organization's own key is validated
431 against this Workspace's own value when it is attached, so if its key policy
432 uses the compartment condition, add this value to it before attaching the key.
422433
423434 - `created_at: string`
424435
from line 475
464475 Workspace. Setting this field requires CMEK to be enabled for your
465476 organization. When set, data stored for this Workspace is encrypted with the
466477 referenced key. Create key configurations with the External Keys API. On
467 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
468 single-Region key in the same AWS account and Region as the Workspace. On that
469 platform the key is validated against this Workspace when it is attached, so a
470 key-policy problem is reported as an error on this request. This field is write-once:
471 once a key is attached to a Workspace it cannot be detached or replaced. To
472 rotate key material, rotate the underlying key on your cloud KMS; the
473 `external_key_id` stays the same.
478 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
479 organization's own key must be a single-Region key in the same AWS account and
480 Region as the Workspace. On that platform the key is validated against this
481 Workspace when it is attached, so a key-policy problem is reported as an error
482 on this request. This field is write-once: once a key is attached to a Workspace
483 it cannot be detached or replaced. To rotate key material, rotate the underlying
484 key on your cloud KMS; the `external_key_id` stays the same.
474485
475486 - `name: string`
476487
from line 491
480491
481492 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
482493
494 - `user_profile_id: string or null`
495
496 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.
497
483498### Example
484499
485500```bash
from line 509
494509 "tags": {
495510 "env": "prod",
496511 "team": "platform"
497 }
512 },
513 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
498514 }'
499515```
500516
from line 534
518534 "env": "prod",
519535 "team": "platform"
520536 },
521 "type": "workspace"
537 "type": "workspace",
538 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
522539}
523540```
524541
from line 583
566583
567584 - `compartment_id: string`
568585
569 Identifier for this Workspace's encryption compartment. When you configure a
570 customer-managed encryption key (CMEK) on AWS, reference this value in your
571 KMS key-policy condition so the key is scoped to this compartment. On GCP and
572 Azure, Anthropic enforces the compartment binding automatically; you do not
573 need to reference this value in your key configuration. See the CMEK
574 integration guide for the required key configuration; unless your organization
575 is on Claude Platform on AWS, it includes a separate value used during key
576 validation. On Claude Platform on AWS there is no separate validation value:
577 the key is validated against this Workspace's own value when it is attached, so
578 if your key policy uses the compartment condition, add this value to it before
579 attaching the key.
586 Identifier for this Workspace's encryption compartment. When you configure an
587 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
588 profile, reference this value in your KMS key-policy condition so the key is
589 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
590 binding automatically; you do not need to reference this value in your key
591 configuration. See the CMEK integration guide for the required key
592 configuration; unless your organization is on Claude Platform on AWS, it
593 includes a separate value used during key validation. On Claude Platform on AWS
594 there is no separate validation value: your organization's own key is validated
595 against this Workspace's own value when it is attached, so if its key policy
596 uses the compartment condition, add this value to it before attaching the key.
580597
581598 - `created_at: string`
582599
from line 639
622639 Workspace. Setting this field requires CMEK to be enabled for your
623640 organization. When set, data stored for this Workspace is encrypted with the
624641 referenced key. Create key configurations with the External Keys API. On
625 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
626 single-Region key in the same AWS account and Region as the Workspace. On that
627 platform the key is validated against this Workspace when it is attached, so a
628 key-policy problem is reported as an error on this request. This field is write-once:
629 once a key is attached to a Workspace it cannot be detached or replaced. To
630 rotate key material, rotate the underlying key on your cloud KMS; the
631 `external_key_id` stays the same.
642 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
643 organization's own key must be a single-Region key in the same AWS account and
644 Region as the Workspace. On that platform the key is validated against this
645 Workspace when it is attached, so a key-policy problem is reported as an error
646 on this request. This field is write-once: once a key is attached to a Workspace
647 it cannot be detached or replaced. To rotate key material, rotate the underlying
648 key on your cloud KMS; the `external_key_id` stays the same.
632649
633650 - `name: string`
634651
from line 655
638655
639656 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
640657
658 - `user_profile_id: string or null`
659
660 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.
661
641662### Example
642663
643664```bash
from line 687
666687 "env": "prod",
667688 "team": "platform"
668689 },
669 "type": "workspace"
690 "type": "workspace",
691 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
670692}
671693```
672694
from line 748
726748 Workspace. Setting this field requires CMEK to be enabled for your
727749 organization. When set, data stored for this Workspace is encrypted with the
728750 referenced key. Create key configurations with the External Keys API. On
729 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
730 single-Region key in the same AWS account and Region as the Workspace. On that
731 platform the key is validated against this Workspace when it is attached, so a
732 key-policy problem is reported as an error on this request. This field is write-once:
733 once a key is attached to a Workspace it cannot be detached or replaced. To
734 rotate key material, rotate the underlying key on your cloud KMS; the
735 `external_key_id` stays the same.
751 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
752 organization's own key must be a single-Region key in the same AWS account and
753 Region as the Workspace. On that platform the key is validated against this
754 Workspace when it is attached, so a key-policy problem is reported as an error
755 on this request. This field is write-once: once a key is attached to a Workspace
756 it cannot be detached or replaced. To rotate key material, rotate the underlying
757 key on your cloud KMS; the `external_key_id` stays the same.
736758
737759- `name: optional string`
738760
from line 766
744766
745767 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
746768
769- `user_profile_id: optional string`
770
771 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. Once set, it can't be replaced or removed (sending the same ID again changes nothing); only deleting the user profile clears it. The default Workspace can't have a user profile.
772
747773### Returns
748774
749775- `BetaWorkspace object`
from line 794
768794
769795 - `compartment_id: string`
770796
771 Identifier for this Workspace's encryption compartment. When you configure a
772 customer-managed encryption key (CMEK) on AWS, reference this value in your
773 KMS key-policy condition so the key is scoped to this compartment. On GCP and
774 Azure, Anthropic enforces the compartment binding automatically; you do not
775 need to reference this value in your key configuration. See the CMEK
776 integration guide for the required key configuration; unless your organization
777 is on Claude Platform on AWS, it includes a separate value used during key
778 validation. On Claude Platform on AWS there is no separate validation value:
779 the key is validated against this Workspace's own value when it is attached, so
780 if your key policy uses the compartment condition, add this value to it before
781 attaching the key.
797 Identifier for this Workspace's encryption compartment. When you configure an
798 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
799 profile, reference this value in your KMS key-policy condition so the key is
800 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
801 binding automatically; you do not need to reference this value in your key
802 configuration. See the CMEK integration guide for the required key
803 configuration; unless your organization is on Claude Platform on AWS, it
804 includes a separate value used during key validation. On Claude Platform on AWS
805 there is no separate validation value: your organization's own key is validated
806 against this Workspace's own value when it is attached, so if its key policy
807 uses the compartment condition, add this value to it before attaching the key.
782808
783809 - `created_at: string`
784810
from line 850
824850 Workspace. Setting this field requires CMEK to be enabled for your
825851 organization. When set, data stored for this Workspace is encrypted with the
826852 referenced key. Create key configurations with the External Keys API. On
827 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
828 single-Region key in the same AWS account and Region as the Workspace. On that
829 platform the key is validated against this Workspace when it is attached, so a
830 key-policy problem is reported as an error on this request. This field is write-once:
831 once a key is attached to a Workspace it cannot be detached or replaced. To
832 rotate key material, rotate the underlying key on your cloud KMS; the
833 `external_key_id` stays the same.
853 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
854 organization's own key must be a single-Region key in the same AWS account and
855 Region as the Workspace. On that platform the key is validated against this
856 Workspace when it is attached, so a key-policy problem is reported as an error
857 on this request. This field is write-once: once a key is attached to a Workspace
858 it cannot be detached or replaced. To rotate key material, rotate the underlying
859 key on your cloud KMS; the `external_key_id` stays the same.
834860
835861 - `name: string`
836862
from line 866
840866
841867 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
842868
869 - `user_profile_id: string or null`
870
871 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.
872
843873### Example
844874
845875```bash
from line 883
853883 "tags": {
854884 "env": "prod",
855885 "team": "platform"
856 }
886 },
887 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
857888 }'
858889```
859890
from line 908
877908 "env": "prod",
878909 "team": "platform"
879910 },
880 "type": "workspace"
911 "type": "workspace",
912 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
881913}
882914```
883915
from line 955
923955
924956 - `compartment_id: string`
925957
926 Identifier for this Workspace's encryption compartment. When you configure a
927 customer-managed encryption key (CMEK) on AWS, reference this value in your
928 KMS key-policy condition so the key is scoped to this compartment. On GCP and
929 Azure, Anthropic enforces the compartment binding automatically; you do not
930 need to reference this value in your key configuration. See the CMEK
931 integration guide for the required key configuration; unless your organization
932 is on Claude Platform on AWS, it includes a separate value used during key
933 validation. On Claude Platform on AWS there is no separate validation value:
934 the key is validated against this Workspace's own value when it is attached, so
935 if your key policy uses the compartment condition, add this value to it before
936 attaching the key.
958 Identifier for this Workspace's encryption compartment. When you configure an
959 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
960 profile, reference this value in your KMS key-policy condition so the key is
961 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
962 binding automatically; you do not need to reference this value in your key
963 configuration. See the CMEK integration guide for the required key
964 configuration; unless your organization is on Claude Platform on AWS, it
965 includes a separate value used during key validation. On Claude Platform on AWS
966 there is no separate validation value: your organization's own key is validated
967 against this Workspace's own value when it is attached, so if its key policy
968 uses the compartment condition, add this value to it before attaching the key.
937969
938970 - `created_at: string`
939971
from line 1011
9791011 Workspace. Setting this field requires CMEK to be enabled for your
9801012 organization. When set, data stored for this Workspace is encrypted with the
9811013 referenced key. Create key configurations with the External Keys API. On
982 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
983 single-Region key in the same AWS account and Region as the Workspace. On that
984 platform the key is validated against this Workspace when it is attached, so a
985 key-policy problem is reported as an error on this request. This field is write-once:
986 once a key is attached to a Workspace it cannot be detached or replaced. To
987 rotate key material, rotate the underlying key on your cloud KMS; the
988 `external_key_id` stays the same.
1014 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
1015 organization's own key must be a single-Region key in the same AWS account and
1016 Region as the Workspace. On that platform the key is validated against this
1017 Workspace when it is attached, so a key-policy problem is reported as an error
1018 on this request. This field is write-once: once a key is attached to a Workspace
1019 it cannot be detached or replaced. To rotate key material, rotate the underlying
1020 key on your cloud KMS; the `external_key_id` stays the same.
9891021
9901022 - `name: string`
9911023
from line 1027
9951027
9961028 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
9971029
1030 - `user_profile_id: string or null`
1031
1032 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.
1033
9981034### Example
9991035
10001036```bash
from line 1060
10241060 "env": "prod",
10251061 "team": "platform"
10261062 },
1027 "type": "workspace"
1063 "type": "workspace",
1064 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
10281065}
10291066```
10301067
from line 1191
11541191
11551192 - `compartment_id: string`
11561193
1157 Identifier for this Workspace's encryption compartment. When you configure a
1158 customer-managed encryption key (CMEK) on AWS, reference this value in your
1159 KMS key-policy condition so the key is scoped to this compartment. On GCP and
1160 Azure, Anthropic enforces the compartment binding automatically; you do not
1161 need to reference this value in your key configuration. See the CMEK
1162 integration guide for the required key configuration; unless your organization
1163 is on Claude Platform on AWS, it includes a separate value used during key
1164 validation. On Claude Platform on AWS there is no separate validation value:
1165 the key is validated against this Workspace's own value when it is attached, so
1166 if your key policy uses the compartment condition, add this value to it before
1167 attaching the key.
1194 Identifier for this Workspace's encryption compartment. When you configure an
1195 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
1196 profile, reference this value in your KMS key-policy condition so the key is
1197 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
1198 binding automatically; you do not need to reference this value in your key
1199 configuration. See the CMEK integration guide for the required key
1200 configuration; unless your organization is on Claude Platform on AWS, it
1201 includes a separate value used during key validation. On Claude Platform on AWS
1202 there is no separate validation value: your organization's own key is validated
1203 against this Workspace's own value when it is attached, so if its key policy
1204 uses the compartment condition, add this value to it before attaching the key.
11681205
11691206 - `created_at: string`
11701207
from line 1247
12101247 Workspace. Setting this field requires CMEK to be enabled for your
12111248 organization. When set, data stored for this Workspace is encrypted with the
12121249 referenced key. Create key configurations with the External Keys API. On
1213 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
1214 single-Region key in the same AWS account and Region as the Workspace. On that
1215 platform the key is validated against this Workspace when it is attached, so a
1216 key-policy problem is reported as an error on this request. This field is write-once:
1217 once a key is attached to a Workspace it cannot be detached or replaced. To
1218 rotate key material, rotate the underlying key on your cloud KMS; the
1219 `external_key_id` stays the same.
1250 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
1251 organization's own key must be a single-Region key in the same AWS account and
1252 Region as the Workspace. On that platform the key is validated against this
1253 Workspace when it is attached, so a key-policy problem is reported as an error
1254 on this request. This field is write-once: once a key is attached to a Workspace
1255 it cannot be detached or replaced. To rotate key material, rotate the underlying
1256 key on your cloud KMS; the `external_key_id` stays the same.
12201257
12211258 - `name: string`
12221259
from line 1263
12261263
12271264 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
12281265
1266 - `user_profile_id: string or null`
1267
1268 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.
1269
12291270### Beta Workspace Member
12301271
12311272- `BetaWorkspaceMember object`
from line 1922
18811922 "data": [
18821923 {
18831924 "type": "workspace_member",
1884 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
1925 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
18851926 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ",
18861927 "workspace_role": "workspace_admin"
18871928 }
from line 2013
19722013 -H 'anthropic-version: 2026-10-21' \
19732014 -H "Authorization: Bearer $ANTHROPIC_API_KEY" \
19742015 -d '{
1975 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
2016 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
19762017 "workspace_role": "workspace_admin"
19772018 }'
19782019```
from line 2023
19822023```json
19832024{
19842025 "type": "workspace_member",
1985 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
2026 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
19862027 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ",
19872028 "workspace_role": "workspace_admin"
19882029}
from line 2100
20592100```json
20602101{
20612102 "type": "workspace_member",
2062 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
2103 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
20632104 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ",
20642105 "workspace_role": "workspace_admin"
20652106}
from line 2197
21562197```json
21572198{
21582199 "type": "workspace_member",
2159 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
2200 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
21602201 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ",
21612202 "workspace_role": "workspace_admin"
21622203}
from line 2259
22182259```json
22192260{
22202261 "type": "workspace_member_deleted",
2221 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
2262 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
22222263 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ"
22232264}
22242265```
from line 2421
23802421
23812422 - `"analytics-usage-cost-2026-08-24"`
23822423
2424 - `"experimental-claude-tag-2026-10-21"`
2425
23832426#### Returns
23842427
23852428- `data: array of BetaServiceAccountWorkspaceMember`
from line 2636
25932636
25942637 - `"analytics-usage-cost-2026-08-24"`
25952638
2639 - `"experimental-claude-tag-2026-10-21"`
2640
25962641#### Body parameters
25972642
25982643- `service_account_id: string`
from line 2867
28222867
28232868 - `"analytics-usage-cost-2026-08-24"`
28242869
2870 - `"experimental-claude-tag-2026-10-21"`
2871
28252872#### Returns
28262873
28272874- `BetaServiceAccountWorkspaceMember object`
from line 3075
30283075
30293076 - `"analytics-usage-cost-2026-08-24"`
30303077
3078 - `"experimental-claude-tag-2026-10-21"`
3079
30313080#### Body parameters
30323081
30333082- `workspace_role: BetaNoBillingWorkspaceRole`
from line 3299
32503299 - `"message-threads-2026-08-12"`
32513300
32523301 - `"analytics-usage-cost-2026-08-24"`
3302
3303 - `"experimental-claude-tag-2026-10-21"`
32533304
32543305#### Returns
32553306
No line in this hunk matches that.