File: beta-headers.md | Updated: 11/15/2025
Agent Skills are now available! Learn more about extending Claude's capabilities with Agent Skills .
English
Search...
Ctrl K
Search...
Navigation
Using the API
Beta headers
Home Developer Guide API Reference Model Context Protocol (MCP) Resources Release Notes
On this page
Beta headers allow you to access experimental features and new model capabilities before they become part of the standard API. These features are subject to change and may be modified or removed in future releases.
Beta headers are often used in conjunction with the beta namespace in the client SDKs
To access beta features, include the anthropic-beta header in your API requests:
Copy
POST /v1/messages
Content-Type: application/json
X-API-Key: YOUR_API_KEY
anthropic-beta: BETA_FEATURE_NAME
When using the SDK, you can specify beta headers in the request options:
Python
TypeScript
cURL
Copy
from anthropic import Anthropic
client = Anthropic()
response = client.beta.messages.create(
model="claude-sonnet-4-5",
max_tokens=1024,
messages=[\
{"role": "user", "content": "Hello, Claude"}\
],
betas=["beta-feature-name"]
)
Beta features are experimental and may:
Multiple beta features
To use multiple beta features in a single request, include all feature names in the header separated by commas:
Copy
anthropic-beta: feature1,feature2,feature3
Version naming conventions
Beta feature names typically follow the pattern: feature-name-YYYY-MM-DD, where the date indicates when the beta version was released. Always use the exact beta feature name as documented.
If you use an invalid or unavailable beta header, youβll receive an error response:
Copy
{
"type": "error",
"error": {
"type": "invalid_request_error",
"message": "Unsupported beta header: invalid-beta-name"
}
}
For questions about beta features:
Remember that beta features are provided βas-isβ and may not have the same SLA guarantees as stable API features.
Was this page helpful?
YesNo
Assistant
Responses are generated using AI and may contain mistakes.