Update an AI integration’s configuration. At least one field must be provided. Omitted fields are left unchanged.
Payload Requirements
name, if provided, must be unique within the account.api_key can be set to null to remove the existing key, or omitted to keep it unchanged.scopings, if provided, replaces all existing scoping rules.provider_metadata, if provided, replaces existing metadata. Set to null to remove.Valid example
{
"name": "Updated Integration",
"model_names": ["gpt-4o", "gpt-4o-mini"]
}
Invalid example (empty body)
{}
Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format
The unique identifier of the AI integration A universally unique identifier
"RW50aXR5OjEyMzQ1"
Body containing AI integration update parameters. At least one field must be provided.
New integration name
The AI provider for this integration
openAI, azureOpenAI, awsBedrock, vertexAI, anthropic, custom, nvidiaNim, gemini New API key. Pass null to remove the existing key. Omit to keep unchanged.
Custom base URL. Pass null to remove.
Supported model names (replaces all)
Custom headers. Pass null to remove.
Enable provider's default model list
Enable function/tool calling
The authentication method for this integration
default, proxy_with_headers, bearer_token Provider-specific configuration
Visibility scoping rules (replaces all existing scopings)
An AI integration object
An AI integration configures access to an external LLM provider (e.g. OpenAI, Azure OpenAI, AWS Bedrock, Vertex AI). Integrations can be scoped to the entire account, a specific organization, or a specific space.
The integration ID
The integration name
The AI provider for this integration
openAI, azureOpenAI, awsBedrock, vertexAI, anthropic, custom, nvidiaNim, gemini Whether an API key is configured (the key itself is never returned)
Whether the provider's default model list is enabled
Whether function/tool calling is enabled
The authentication method for this integration
default, proxy_with_headers, bearer_token Visibility scoping rules
When the integration was created
When the integration was last updated
The user ID of the user who created the integration
Custom base URL for the provider
Supported model names
Custom headers included in requests
Provider-specific configuration (AWS or GCP metadata)