Skip to main content
The integrations client methods are currently in ALPHA. The API may change without notice. A one-time warning is emitted on first use.
Manage Arize integrations. Integrations are polymorphic: LLM integrations configure a model provider (OpenAI, Anthropic, Gemini, AWS Bedrock, Custom, Vertex AI, NVIDIA NIM, LiteLLM, Fireworks, or Together AI), while AGENT integrations connect a customer-hosted agent exposed at an HTTPS endpoint.

Key Capabilities

  • List integrations of every type, or filter to a single type
  • Retrieve an integration by name or ID
  • Create LLM integrations for any supported provider
  • Create agent integrations for customer-hosted agents
  • Update LLM or agent integrations without replacing the entire resource
  • Delete integrations

Integration Types

Integration names are unique per (account, type). When resolving an integration by name, pass integration_type to disambiguate.

List Integrations

List all integrations you have access to. When integration_type is omitted, integrations of every type are returned in one merged list (most recently created first).
For details on pagination, field introspection, and data conversion (to dict/JSON/DataFrame), see Response Objects.

Create an LLM Integration

Create an LLM integration by passing the provider-specific config. All 10 providers are supported — construct the matching Create*Config for the provider you want.

OpenAI

Anthropic

AWS Bedrock

AWS Bedrock nests an auth config (CreateAwsBedrockDefaultAuth, CreateAwsBedrockBearerTokenAuth, or CreateAwsBedrockProxyWithHeadersAuth).
The remaining providers use CreateGeminiConfig, CreateCustomConfig, CreateVertexAiConfig, CreateNvidiaNimConfig, CreateLiteLlmConfig, CreateFireworksConfig, and CreateTogetherAiConfig. A pre-wrapped CreateLlmConfig union is also accepted.

Create an Agent Integration

Agent integrations connect a customer-hosted agent exposed at an HTTPS endpoint. Provide a JSON Schema (Draft-07) describing the endpoint’s request body.

Get an Integration

Retrieve an integration by name or ID. When resolving by name, pass integration_type (names are unique per (account, type)).

Update an LLM Integration

Only the fields you pass are sent to the server; omitted fields are left unchanged. The provider is immutable, and config fields are provider-conditional (the server rejects fields that don’t apply to the stored provider). Pass None to clear a nullable field (api_key, base_url, headers).

Update an Agent Integration

Only the fields you pass are sent; omitted fields are left unchanged. Collection fields (headers, request_presets, scopings) replace the existing values when provided. Pass None to clear a nullable field (description, headers).

Delete an Integration

Delete an integration by name or ID. This operation is irreversible. When resolving by name, pass integration_type.