List User Profiles changedapi/beta/user_profiles/list
Nearest release: v2.1.238, published under 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+48added
Lines−37removed
From line
35
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits20to this page, all time
The whole hunk
from line 35, old and new numbered
/
from line 35
3535
3636 - `string`
3737
38 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 30 more`
38 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 31 more`
3939
4040 - `"message-batches-2024-09-24"`
4141
from line 81
8181
8282 - `"user-profiles-2026-03-24"`
8383
84 - `"user-profiles-2026-08-18"`
85
8486 - `"advisor-tool-2026-03-01"`
8587
8688 - `"managed-agents-2026-04-01"`
from line 123
121123
122124 Arbitrary key-value metadata. Maximum 16 pairs, keys up to 64 chars, values up to 512 chars.
123125
124 - `relationship: "external" or "resold" or "internal"`
125
126 How the entity behind a user profile relates to the platform that owns the API key. `external`: an individual end-user of the platform. `resold`: a company the platform resells Claude access to. `internal`: the platform's own usage.
127
128 - `"external"`
129
130 - `"resold"`
131
132 - `"internal"`
133
134126 - `trust_grants: map[BetaUserProfileTrustGrant]`
135127
136128 Trust grants for this profile, keyed by grant name. Key omitted when no grant is active or in flight.
from line 147
155147
156148 A timestamp in RFC 3339 format
157149
150 - `access_type: optional "application" or "passthrough"`
151
152 How the platform uses the API on behalf of the entity this profile represents. `application`: the platform sells a product that uses the API behind the scenes, and the profile represents an individual end-user of that product. `passthrough`: the platform resells raw inference, and the profile identifies the resold-to company.
153
154 - `"application"`
155
156 - `"passthrough"`
157
158158 - `external_id: optional string or null`
159159
160160 Platform's own identifier for this user. Not enforced unique.
from line 161
161161
162162 - `name: optional string or null`
163163
164 Display name of the entity this profile represents. For `resold` this is the resold-to company's name.
164 Real-world name of the entity this profile represents (company or individual). For a resold-to company (`access_type` `passthrough`, or `relationship` `resold` under the `user-profiles-2026-03-24` header) this is that company's name.
165165
166 - `relationship: optional "external" or "resold" or "internal"`
167
168 How the entity behind a user profile relates to the platform that owns the API key. `external`: an individual end-user of the platform. `resold`: a company the platform resells Claude access to. `internal`: the platform's own usage.
169
170 - `"external"`
171
172 - `"resold"`
173
174 - `"internal"`
175
166176- `next_page: string or null`
167177
168178 Cursor for the next page, or `null` when there are no more results.
from line 182
172182```http
173183curl https://api.anthropic.com/v1/user_profiles \
174184 -H 'anthropic-version: 2023-06-01' \
175 -H 'anthropic-beta: user-profiles-2026-03-24' \
185 -H 'anthropic-beta: user-profiles-2026-08-18' \
176186 -H "X-Api-Key: $ANTHROPIC_API_KEY"
177187```
178188
from line 195
185195 "id": "uprof_011CZkZCu8hGbp5mYRQgUmz9",
186196 "created_at": "2026-03-15T10:00:00Z",
187197 "metadata": {},
188 "relationship": "external",
189198 "trust_grants": {
190199 "cyber": {
191200 "status": "active"
from line 202
193202 },
194203 "type": "user_profile",
195204 "updated_at": "2026-03-15T10:00:00Z",
205 "access_type": "application",
196206 "external_id": "user_12345",
197 "name": "Example User"
207 "name": "Example User",
208 "relationship": "external"
198209 }
199210 ],
200211 "next_page": "page_MjAyNS0wNS0xNFQwMDowMDowMFo="
No line in this hunk matches that.