Audio files now included in C2PA Content Credentials support for code execution outputs
Developers using Claude's code execution tool can now retrieve audio files with C2PA Content Credentials through the Files API, expanding the types of media files that carry content authenticity markers.
Evidence
−supported image and video files that Claude produces through the code execution tool carry C2PA Content Credentials
+supported image, video, and audio files that Claude produces through the code execution tool carry C2PA Content Credentials
Claude Enterprise Admin API, Analytics API, and Compliance API now require anthropic-version header on all requests
Developers using Claude Enterprise Admin API, Analytics API, or Compliance API must now include the anthropic-version header in every request to these endpoints, matching the requirement for the rest of the Claude API.
+The guides for the Claude Enterprise endpoints of the Admin API (user management and spend limits), the Claude Enterprise Analytics API, and the Compliance API now show the anthropic-version header; send it on every request to these endpoints, as in the rest of the Claude API. See API versions.
Ask Docs
Admin API now available in CLI and multiple SDK languages
Organization administrators can now manage organization settings, members, workspaces, API keys, rate limits, and other admin functions through ant CLI and Python, TypeScript, C#, Go, Java, PHP, and Ruby SDKs instead of curl-only access.
Evidence
+The Admin API is now available in the ant CLI and the Python, TypeScript, C#, Go, Java, PHP, and Ruby SDKs under client.beta.organization. They cover organization info, members, invites, workspaces and workspace members, API keys, rate limits, service accounts, workload identity federation issuers and rules, and customer-managed encryption keys.
Admin API user-management endpoints for Claude Enterprise are now generally available
Organizations using Claude Enterprise can now manage users, invites, groups, and custom roles via the Admin API without beta headers.
Evidence
+The Admin API user-management endpoints for Claude Enterprise (claude.ai) organizations (members, invites, groups, and custom roles) are now generally available. The anthropic-beta: ce-user-management-2026-07-13 header is no longer required on group and custom-role requests
Clarity added: Claude Haiku 3.5 retirement is API-specific, not universal
Developers using Claude Haiku 3.5 on Amazon Bedrock or Google Cloud can continue using it; only Claude API users need to migrate to Claude Haiku 4.5.
Evidence
−We've retired the Claude Sonnet 3.7 model (claude-3-7-sonnet-20250219) and the Claude Haiku 3.5 model (claude-3-5-haiku-20241022). All requests to these models will now return an error.
+We've retired the Claude Sonnet 3.7 model (claude-3-7-sonnet-20250219) and the Claude Haiku 3.5 model (claude-3-5-haiku-20241022). All requests to Claude Sonnet 3.7 will now return an error. Requests to Claude Haiku 3.5 on the Claude API will now return an error; it remains available on Amazon Bedrock and Google Cloud.
New anthropic-workspace-id response header added to Claude API
Developers can now identify the workspace behind an API response using the new wrkspc_-prefixed header, enabling better workspace management and organization tracking.
Evidence
+We've added the anthropic-workspace-id response header to the Claude API. It carries the wrkspc_-prefixed ID of the workspace that the request's API key or access token resolved to, including your organization's Default Workspace. See Identify the workspace behind an API response.
Compliance API expanded to support local sessions from Cowork and Claude Code
Claude Enterprise organizations can now retrieve transcripts and metadata from Cowork and Claude Code sessions running locally on users' machines using new endpoints: GET /v1/compliance/apps/sessions/local, GET /v1/compliance/apps/sessions/local/{session_id}, and GET /v1/compliance/apps/sessions/local/{session_id}/messages.
Evidence
+The Compliance API now returns transcripts of Cowork and Claude Code sessions that run on your users' machines, in beta for Claude Enterprise organizations. GET /v1/compliance/apps/sessions/local lists sessions across your organization, GET /v1/compliance/apps/sessions/local/{session_id} retrieves one session's metadata, and GET /v1/compliance/apps/sessions/local/{session_id}/messages returns its transcript
Removal of introductory pricing notation and terms for Claude API
Developers will no longer see the explicit introductory pricing rates ($2/$10) and the sunset date (August 31, 2026), or the standard pricing thereafter ($3/$15). This could affect pricing decisions and understanding of rate changes.
Evidence
−Input*
Output*
Write*
Read*
*Introductory pricing of $2/$10 per million input/output tokens through August 31, 2026; $3/$15 standard pricing thereafter.
Claude Opus 4.1 (claude-opus-4-1-20250805) model retired
Users and applications using Claude Opus 4.1 will receive errors and must migrate to Claude Opus 5. Researchers can apply for continued access through the External Researcher Access Program.
Evidence
+We've retired the Claude Opus 4.1 model (claude-opus-4-1-20250805). All requests to this model will now return an error. We recommend upgrading to Claude Opus 5. Researchers can request ongoing access through the External Researcher Access Program.
Claude Managed Agents update semantics now make version field optional
Users can now update agents without providing a version (unconditional update) or supply it for optimistic concurrency control with 409 error on mismatch.
Evidence
+The version field is now optional when updating a Claude Managed Agents agent. Supply it for optimistic concurrency (a mismatch returns a 409 error), or omit it to apply the update unconditionally. See Update semantics.
Users will lose access to the legacy Workbench (platform.claude.com/workbench) in the Claude Console. Saved prompts, variables, and evals from the old Workbench are not supported in the updated version. Users need to export any data they want to keep before August 17, 2026.
Evidence
+The legacy Workbench (platform.claude.com/workbench) in the Claude Console is being sunset with access ending on August 17, 2026. Saved prompts, variables, and evals are not supported in the updated Workbench. You can export any data you want to keep from the banner and under your Organizational Settings.
Mid-conversation system messages feature now generally available across multiple Claude models and platforms
Developers using Claude Fable 5, Claude Mythos 5, and Claude Opus 4.8 can now use mid-conversation system messages without beta headers on Claude API, Amazon Bedrock, and Google Cloud.
Evidence
+Mid-conversation system messages are available on Claude Fable 5, Claude Mythos 5, and Claude Opus 4.8, on the Claude API, Claude in Amazon Bedrock, and Google Cloud. No beta header is required.