Claude Enterprise API documentation now requires the anthropic-version header
The documentation for Admin API, Analytics API and Compliance API for Claude Enterprise has been updated — it now explicitly requires the anthropic-version header for every request to these endpoints.
Anthropic updated the documentation for three groups of endpoints intended for Claude Enterprise: Admin API (management of users and spending limits), Analytics API and Compliance API. The guides now explicitly state that the anthropic-version header must be sent with every request to these endpoints, just as it is for the rest of Claude API.
The source links to the general API versions documentation, which explains header-based versioning in more detail. The source does not provide specific version values or further technical details. You can find more information in the source article.
Why it matters
This affects developers and administrators who use these APIs to manage users, spending limits, analytics or compliance in the Claude Enterprise environment. Without a correctly configured header, requests to the endpoints may fail or behave inconsistently, so existing integrations need to be checked and adjusted if necessary.
Two audiences, two different impacts
What this means
For individuals
Developers and administrators working with these APIs must add the anthropic-version header to their requests; otherwise, endpoint calls may not work correctly.
For a business
Companies using Claude Enterprise API integrations (user management, spending limits, analytics, compliance) must verify that their implementation sends the anthropic-version header; otherwise, endpoint calls may fail.
DevelopmentCheck the original
Event sources
only one source so far · 1 publisher, 0 independent. We count feeds from the same owner only once.