What changed
Anthropic’s October 20 release notes introduce Claude API user profiles and organization webhooks. For developers serving multiple customers, a profile identifies the end customer behind a request. This is application infrastructure, not a new Claude chat setting.
Create a profile once, then attach its returned ID through the anthropic-user-profile-id request header. Profile creation is not idempotent: retrying creation can produce another profile. Profiles are not billable and API pricing is unchanged. Anthropic recommends separate organizations for customer-facing and internal traffic, rather than relying on workspaces for that separation.
The webhook format is preparation, not a working alert
The current organization-webhook guide explicitly says event delivery is not live: Anthropic does not send the two documented events, so a registered endpoint receives nothing. Developers can register endpoints and prepare a handler from the documented format. The beta requires account-team access and excludes HIPAA-ready organizations.
Profiles can scope safety enforcement to an individual customer, but this does not guarantee uninterrupted service for everyone else. Available profile fields and actions also depend on organization enablement.
Our take
For gateway builders and experienced technicians, accurate customer attribution is the practical opportunity. Check that each request carries the intended profile, including retries and background jobs. Keep internal workloads separate, and avoid treating a profile as permission to relax existing safeguards.
Do not replace an existing monitoring process with these webhooks. If delivery becomes available for your organization, confirm it actually works before relying on alerts. Follow signature-verification guidance, fetch the current profile, and plan for delayed, duplicate, out-of-order, or missed notifications with catch-up polling.
We have not created profiles, registered an endpoint, called the API, or tested enforcement. The vendor dates the announcement October 20; its exact posting hour was not established. Availability statements here reflect the documentation checked for this briefing.