About static HTTP headers
A Server Workload: Server Workloads represent target services, APIs, databases, or applications that receive and respond to access requests from Client Workloads.Learn more can define static HTTP headers: fixed header name and value pairs that Agent Proxy adds to every HTTP request it forwards to that workload.
The Static HTTP Headers section appears when the Server Workload’s Service Endpoint has Application Protocol set to HTTP, which covers most REST and web API targets.
Static HTTP headers belong to the Server Workload, so they apply to every Access Policy that reaches it. Agent Proxy sends them whether or not the policy uses a Credential Provider: Credential Providers obtain the specific access credentials—such as API keys, OAuth tokens, or temporary cloud credentials—that Client Workloads need to authenticate to Server Workloads.Learn more to inject a credential.
When to use static HTTP headers
Section titled “When to use static HTTP headers”Use static HTTP headers when a target service requires a header on every request and your application doesn’t send it.
For example, Claude’s API requires an anthropic-version header, such as anthropic-version: 2023-06-01.
Common cases:
- Pin requests to a specific API version
- Identify your account or tenant on the target service, not your Aembit Tenant
- Direct requests through custom routing