Send a Forge API key as an HTTP bearer token:
The service resolves the Weights & Biases viewer, default entity, and team memberships on every management request. The proxy caches the same identity by a hash of the key.
Management entity selection
Omit the entity header to use the key’s default entity. GET /projects and GET /projects/summaries are the exception: without the header, they list projects across every entity that the key can access.
The following request lists projects across all accessible entities:
Select an accessible team with one header:
Entity query parameters are rejected. This prevents resource filters from being confused with ownership.
Proxy entity selection
Proxy requests select the entity and the project together with the OpenAI-Project: <entity>/<project> header, where <project> is the project’s Weights & Biases project name. The OpenAI SDKs send this header from the project client option or the OPENAI_PROJECT_ID environment variable, so you don’t need custom header configuration:
Because the header names the entity, a personal API key can call a team project without changing its default entity. Before it looks up the project, the proxy checks that the key can access the entity. If the key can’t access the entity, the proxy returns 403.
A value that isn’t in <entity>/<project> form returns 400. For example, an OpenAI project ID such as proj_abc123, often left over in OPENAI_PROJECT_ID, returns 400 with a hint to unset or change the variable.
Production credentials
Prefer a Weights & Biases team service-account key for deployed applications and long-running jobs. Personal credentials couple availability to one employee’s access and default to that employee’s personal entity. Last modified on October 26, 2026
