Wirestack
Claude API adds user profiles: tag each request with your end customer (October 20, 2026)
New /v1/user_profiles endpoints let platforms tag requests by end customer, so enforcement hits one profile, not the whole org.
Your keys
0 of 1 ready
Create each key on its own page, paste it below, then copy the finished lines into your project's .env file. What you paste stays in this tab. It is never sent to Wirestack or saved.
- Anthropic API keyANTHROPIC_API_KEYGet key
Click Create key. It starts with sk-ant- and is shown only once
What you get
On October 20, 2026 Anthropic launched user profiles. You register each end customer once with POST /v1/user_profiles, keep the uprof_ ID it returns, and send it in the anthropic-user-profile-id header on every request made for that customer. The SDKs add the header for you through a user_profile_id argument.
If Anthropic restricts or bans one of your end customers, the action can then apply to that profile instead of your whole organization. Profiles are not billed.
The same day Anthropic added organization webhooks to the Admin API, in beta with the webhooks-2026-10-07 header. They tell you when a profile is restricted or banned, and when that ends. Access is by request through your Anthropic account team.
Prerequisites
- An Anthropic API key in
ANTHROPIC_API_KEY - An app that sends Claude requests on behalf of your own customers
Steps
- Create one profile per end customer when they sign up.
POST /v1/user_profilesis not idempotent, so store the ID and reuse it. - Pass
user_profile_idon Messages API calls made for that customer. - Keep your own internal usage in a separate organization. Requests without a profile ID count as your organization's own usage.
Test it
Create a profile, send one message with its ID, and check the request succeeds.
Not confirmed
- When organization webhooks leave beta.