Content-Type and the providerβs authentication reach the guardrail endpoint. All other client headers stop at Portkey.
Configuration
AddforwardHeaders to any external checkβs parameters. List the exact header names you want forwarded:
forwardHeaders is absent or omitted, nothing is forwarded. Each check configures forwarding independently.
Provider authentication headers always take precedence β forwarded headers cannot overwrite them.
If you include
traceparent in your list and the client sends x-portkey-trace-id but no traceparent, Portkey synthesizes a valid W3C traceparent automatically. If the client sends a valid traceparent directly, it passes through unchanged.Restricted Headers
Portkey prevents forwarding headers that carry credentials or sensitive context. The following categories are blocked and rejected at save time:- Credentials β
authorization,x-api-key,ocp-apim-subscription-key,proxy-authorization - Session β
cookie - Cloud metadata β headers used by cloud IMDS endpoints (AWS, GCP)
- Internal routing β all
x-portkey-*headers exceptx-portkey-trace-idandx-portkey-span-id - Hop-by-hop β protocol headers like
connection,host,transfer-encoding
Related
Guardrails
Bring Your Own Guardrails
Portkey is now PRISMA AIRS AI Gateway. See it in action.
Contact Us

