Create User Profile changedapi/beta/user_profiles/create
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+58added
Lines−39removed
From line
17
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 17, old and new numbered
/
from line 17
1717
1818 - `string`
1919
20 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 30 more`
20 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 31 more`
2121
2222 - `"message-batches-2024-09-24"`
2323
from line 63
6363
6464 - `"user-profiles-2026-03-24"`
6565
66 - `"user-profiles-2026-08-18"`
67
6668 - `"advisor-tool-2026-03-01"`
6769
6870 - `"managed-agents-2026-04-01"`
from line 89
8789
8890### Body Parameters
8991
92- `access_type: optional "application" or "passthrough"`
93
94 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.
95
96 - `"application"`
97
98 - `"passthrough"`
99
90100- `external_id: optional string or null`
91101
92102 Platform's own identifier for this user. Not enforced unique. Maximum 255 characters.
from line 107
97107
98108- `name: optional string or null`
99109
100 Display name of the entity this profile represents. Required when relationship is `resold` (the resold-to company's name); optional otherwise. Maximum 255 characters.
110 Optional for all profiles. Real-world name of the entity this profile represents (company or individual); for a resold-to company (`relationship` `resold` / `access_type` `passthrough`), that company's name where known. Maximum 255 characters.
101111
102112- `relationship: optional "external" or "resold" or "internal"`
103113
from line 121
111121
112122### Returns
113123
114- `BetaUserProfile object { id, created_at, metadata, 6 more }`
124- `BetaUserProfile object { id, created_at, metadata, 7 more }`
115125
116126 - `id: string`
117127
from line 135
125135
126136 Arbitrary key-value metadata. Maximum 16 pairs, keys up to 64 chars, values up to 512 chars.
127137
128 - `relationship: "external" or "resold" or "internal"`
129
130 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.
131
132 - `"external"`
133
134 - `"resold"`
135
136 - `"internal"`
137
138138 - `trust_grants: map[BetaUserProfileTrustGrant]`
139139
140140 Trust grants for this profile, keyed by grant name. Key omitted when no grant is active or in flight.
from line 159
159159
160160 A timestamp in RFC 3339 format
161161
162 - `access_type: optional "application" or "passthrough"`
163
164 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.
165
166 - `"application"`
167
168 - `"passthrough"`
169
162170 - `external_id: optional string or null`
163171
164172 Platform's own identifier for this user. Not enforced unique.
from line 173
165173
166174 - `name: optional string or null`
167175
168 Display name of the entity this profile represents. For `resold` this is the resold-to company's name.
176 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.
169177
178 - `relationship: optional "external" or "resold" or "internal"`
179
180 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.
181
182 - `"external"`
183
184 - `"resold"`
185
186 - `"internal"`
187
170188### Example
171189
172190```http
from line 191
173191curl https://api.anthropic.com/v1/user_profiles \
174192 -H 'Content-Type: application/json' \
175193 -H 'anthropic-version: 2023-06-01' \
176 -H 'anthropic-beta: user-profiles-2026-03-24' \
194 -H 'anthropic-beta: user-profiles-2026-08-18' \
177195 -H "X-Api-Key: $ANTHROPIC_API_KEY" \
178196 -d '{
179197 "external_id": "user_12345",
from line 206
188206 "id": "uprof_011CZkZCu8hGbp5mYRQgUmz9",
189207 "created_at": "2026-03-15T10:00:00Z",
190208 "metadata": {},
191 "relationship": "external",
192209 "trust_grants": {
193210 "cyber": {
194211 "status": "active"
from line 213
196213 },
197214 "type": "user_profile",
198215 "updated_at": "2026-03-15T10:00:00Z",
216 "access_type": "application",
199217 "external_id": "user_12345",
200 "name": "Example User"
218 "name": "Example User",
219 "relationship": "external"
201220}
202221```
203222
No line in this hunk matches that.