Unified Api And Gateway Proxy

Team migrates an existing OpenAI-SDK app to Portkey by changing only base_url to https://api.portkey.ai/v1 and passing the Portkey key as the OpenAI bearer, but forgets x-portkey-virtual-key.

Set base_url=https://api.portkey.ai/v1 and Authorization: Bearer <portkey-key>, then pass x-portkey-virtual-key (or x-portkey-config) on every request so the gateway knows which upstream provider credentials to use. Without a virtual key or config, the gateway returns an error rather than silently …

Native Portkey SDK call omits the x-portkey-api-key header and relies on an environment variable from a prior process; the value is unset in the deployed container.

Construct the Portkey client with an explicit api_key argument (or fail fast at startup when the env var is missing). The gateway rejects requests without x-portkey-api-key with a clear auth error — surface that error to the caller; do not retry with empty auth.

Operator needs Anthropic-only fields (top_k, anthropic-beta header for prompt caching) on a Portkey-proxied request.

Per Portkey docs, provider-specific parameters can be passed in the body and provider-specific headers via the request headers; Portkey forwards them to the matched upstream. Verify by reading the request log to confirm the header reached the provider. [REQUIRES-VERIFICATION] for the current list o…