Create an integration
Create a new integration. The type field selects the config shape;
for LLM, config.provider selects the per-provider config. v1
supports type=LLM (provider OPEN_AI) and type=AGENT.
Authorizations
Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format
Body
Create a new integration. The type field selects the config shape; for
LLM, config.provider selects the per-provider config.
Payload Requirements
type,name, andconfigare required.namemust be unique within the account for the giventype.scopingsdefaults to account-wide visibility when omitted.- Type- and provider-specific rules (required fields, defaults, write-only
secrets) are documented on each config schema: see the per-provider
members of
CreateLlmConfigfortype: LLM, andCreateAgentConfigfortype: AGENT.
Valid example
Invalid example (missing required config)
Invalid example (missing required config.provider for type: LLM)
- Option 1
- Option 2
LLM Integration name. Unique per (account, type).
Create config for an OpenAI LLM integration. api_key is required and is write-only (never returned in responses).
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
Visibility scoping rules. Defaults to account-wide.
Response
An integration object.
- Option 1
- Option 2
An LLM integration (type=LLM).
The unique identifier for the integration.
Discriminator identifying an LLM integration.
LLM The integration name. Unique per (account, type).
Visibility scoping rules. Account-wide when empty.
When the integration was created.
When the integration was last updated.
Unique identifier of the user who created the integration.
Config for an OpenAI LLM integration.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7