Beta headers

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.

How to use beta headers

To access beta features, include the anthropic-beta header in your API requests:

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:

client = Anthropic()

response = client.beta.messages.create(
    model="claude-opus-4-7",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Hello, Claude"}],
    betas=["files-api-2025-04-14"],
)

Multiple beta features

To use multiple beta features in a single request, include all feature names in the header separated by commas:

anthropic-beta: feature1,feature2,feature3

Endpoint-specific headers

Some beta features are scoped to specific endpoints rather than individual request parameters and require a feature-specific beta header on every request:

See the Managed Agents overview for details.

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.

Error handling

If you use an invalid or unavailable beta header, you'll receive an error response:

{
  "type": "error",
  "error": {
    "type": "invalid_request_error",
    "message": "Unsupported beta header: invalid-beta-name"
  }
}

Getting help

For questions about beta features:

1. Check the documentation for the specific feature
2. Review the API changelog for updates
3. Contact support for assistance with production usage

Remember that beta features are provided "as-is" and may not have the same SLA guarantees as stable API features.