Get User Profile changedapi/beta/user_profiles/retrieve
Nearest release: v2.1.306, published 2 hours 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+18added
Lines−18removed
From line
25
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits19to this page, all time
The whole hunk
from line 25, old and new numbered
/
from line 25
2525
2626- `"anthropic-beta": optional array of AnthropicBeta`
2727
28 This endpoint is in beta: requests must send `user-profiles-2026-03-24`, `user-profiles-2026-08-18`, or `user-profiles-2026-09-04` in this header.
28 Optional header to specify the beta version(s) you want to use.
2929
3030 - `string`
3131
from line 163
163163
164164 Arbitrary key-value metadata. Maximum 16 pairs, keys up to 64 chars, values up to 512 chars.
165165
166 - `name: string or null`
167
168 Real-world name of the entity this profile represents (company or individual). For a company the platform resells Claude access to (`access_type` `passthrough`) this is that company's name. `null` until the platform supplies one.
169
166170 - `trust_grants: map[BetaUserProfileTrustGrant]`
167171
168172 Trust grants for this profile, keyed by grant name. Key omitted when no grant is active or in flight.
from line 183
179183
180184 - `updated_at: string`
181185
182 When this user profile was last modified, in RFC 3339 format. Trust-grant status changes also bump this timestamp.
186 When this user profile was last modified, in RFC 3339 format. It normally also updates shortly after Anthropic gives the profile an approval or withdraws one. Other changes to the statuses that Anthropic reports do not always update it, so read the status itself rather than watching this timestamp.
183187
184188 format: date-time
185189
186190 - `access_type: optional "application" or "passthrough"`
187191
188 How the platform uses the API for this entity: `application` (default) or `passthrough`. Present under the `user-profiles-2026-08-18` and later beta headers.
192 How the platform uses the API for this entity: `application` (default) or `passthrough`. Absent under the legacy `user-profiles-2026-03-24` beta header.
189193
190194 - `"application"`
191195
from line 201
197201
198202 - `external_id: optional string or null`
199203
200 Platform's own identifier for this user. Not enforced unique. Present under the `user-profiles-2026-03-24` and `user-profiles-2026-08-18` beta headers; under `user-profiles-2026-09-04` the value is `external_user_details.reference_id`.
204 Platform's own identifier for this user. Not enforced unique. Legacy field, present only under the `user-profiles-2026-03-24` and `user-profiles-2026-08-18` beta headers; without one of them, the value is `external_user_details.reference_id`.
201205
202206 - `external_user_details: optional BetaUserProfileExternalUserDetails`
203207
204 Details about the entity this profile represents, as the platform states them; not verified by Anthropic. Present under the `user-profiles-2026-09-04` beta header, with every field present and `null` until the platform supplies a value; the earlier beta headers serve `reference_id` as the top-level `external_id`, and `user-profiles-2026-08-18` serves `onboarded_at` as `external_user_onboarded_at`.
208 Details about the entity this profile represents, as the platform states them; not verified by Anthropic. Every field is present, `null` until the platform supplies a value. Absent under the legacy `user-profiles-2026-03-24` and `user-profiles-2026-08-18` beta headers, which serve `reference_id` as the top-level `external_id` and, under `user-profiles-2026-08-18`, `onboarded_at` as `external_user_onboarded_at`.
205209
206210 - `account_status: "active" or "suspended" or "blocked" or null`
207211
from line 259
255259
256260 - `external_user_onboarded_at: optional string or null`
257261
258 When the entity this profile represents opened its account with the platform, as stated by the platform, in RFC 3339 format (UTC). `null` until the platform supplies one. Present under the `user-profiles-2026-08-18` beta header; under `user-profiles-2026-09-04` the value is `external_user_details.onboarded_at`.
262 When the entity this profile represents opened its account with the platform, as stated by the platform, in RFC 3339 format (UTC). `null` until the platform supplies one. Legacy field, present only under the `user-profiles-2026-08-18` beta header; without a legacy header, the value is `external_user_details.onboarded_at`.
259263
260264 format: date-time
261265
262 - `name: optional string or null`
263
264 Real-world name of the entity this profile represents (company or individual). For a company the platform resells Claude access to (`access_type` `passthrough`) this is that company's name.
265
266266## Example
267267
268268```bash
from line 279
279279 "id": "uprof_011CZkZCu8hGbp5mYRQgUmz9",
280280 "created_at": "2026-03-15T10:00:00Z",
281281 "metadata": {},
282 "name": "Example User",
282283 "trust_grants": {
283284 "cyber": {
284285 "status": "active"
from line 291
290291 "external_id": "user_12345",
291292 "external_user_details": {
292293 "account_status": "active",
293 "country": "country",
294 "email_hash": "email_hash",
295 "entity_type": "individual",
296 "name_hash": "name_hash",
297 "onboarded_at": "2019-12-27T18:11:19.117Z",
298 "reference_id": "reference_id"
294 "country": "US",
295 "email_hash": null,
296 "entity_type": "business",
297 "name_hash": null,
298 "onboarded_at": "2024-11-02T08:15:00Z",
299 "reference_id": "user_12345"
299300 },
300 "external_user_onboarded_at": "2024-11-02T08:15:00Z",
301 "name": "Example User"
301 "external_user_onboarded_at": "2024-11-02T08:15:00Z"
302302}
303303```
304304
No line in this hunk matches that.