Create a Provider
Creates a new named provider. Either supply a connection_id to share
an existing credential, or supply api_key / credentials to create
an inline secret as part of the request.
Pass models to enable a list of upstream model names as 1:1 routes
in the same call — equivalent to creating each route individually
afterwards.
- Inline credential — pass
api_key(orcredentials) directly. Barndoor stores the secret in its encrypted secret store, scoped to this provider. - Shared credential — pass
connection_idreferencing an existing Credential. The provider’sauth_type,base_url, and settings inherit from the shared record.
Auto-enabling models in one call
Pass a list of upstream model names inmodels and Barndoor will create a 1:1
Model Route for each
one in the same call. The route’s alias matches the upstream model name so
callers can address it as <provider>/<model>. Add bare-name aliases or
failover routes afterwards via the Model Routes endpoints.
Example
Authorizations
JWT obtained through Barndoor's authentication flow. Pass the token
verbatim in Authorization: Bearer <token>. Use the Barndoor SDK's
loginInteractive() helper to obtain a token in scripts and notebooks.
Body
Slug of the upstream model provider this resource speaks to
openai, anthropic, azure_openai, google_ai, bedrock, vertex, groq, together, mistral, cohere, xai, fireworks, perplexity, openrouter, deepseek, custom "openai"
The authentication scheme this credential or provider uses to talk to
the upstream model provider. Valid values depend on model_provider:
for OpenAI/Anthropic-style vendors this is typically api_key; for AWS
Bedrock it is one of aws_role, aws_keys, or bedrock_api_key; for
Google Vertex it is google_adc, google_service_account, or
google_impersonation; Anthropic OAuth passthrough uses oauth_passthrough.
"api_key"
Required for direct API-key auth when no connection_id is provided
Optional reference to a provider catalog template
Optional reference to a shared Credentials record
Upstream models to enable on this provider as 1:1 model routes.
Each entry creates a route where the alias equals the upstream model
name (so callers can address it as <provider>/<model>).
["gpt-4o-mini", "gpt-4o"]Structured non-API-key credentials (AWS keys, Vertex SA JSON, etc.)
1 <= x <= 36001 <= x <= 1800Response
The newly created provider
A named upstream provider backed by a credential and a model family.
"OpenAI Production (US)"
Slug of the upstream model provider this resource speaks to
openai, anthropic, azure_openai, google_ai, bedrock, vertex, groq, together, mistral, cohere, xai, fireworks, perplexity, openrouter, deepseek, custom "openai"
The authentication scheme this credential or provider uses to talk to
the upstream model provider. Valid values depend on model_provider:
for OpenAI/Anthropic-style vendors this is typically api_key; for AWS
Bedrock it is one of aws_role, aws_keys, or bedrock_api_key; for
Google Vertex it is google_adc, google_service_account, or
google_impersonation; Anthropic OAuth passthrough uses oauth_passthrough.
"api_key"
Reference to a built-in provider catalog template, if used
Reference to a shared Credentials record, if any
Provider-tier total-request timeout override. When null (the
default) the gateway inherits the platform default. Affects every
route served by this provider unless a more specific Model Route
value overrides it.
1 <= x <= 3600Maximum allowed idle gap between streamed response chunks. null
inherits the platform default.
1 <= x <= 1800Catalog slug shorthand used in some response listings
