- View Connections – Required for viewing connection details
- Manage Connections – Required for creating and updating connections
Base URL
Common Request Headers
API List
List All Connections
Retrieves a list of all configured connections with optional filtering.Query Parameters
Sample Request
Sample Response
Get Connection by ID
Retrieves the details of a specific connection using its unique identifier.Path Parameters
Sample Request
Sample Response
Create Connection
Creates a new connection to an external model provider. Supports creation of Custom API, OpenAI, Azure OpenAI, Anthropic, and other external model connections.
Body Parameters
Sample Request – Custom API Connection - Default Provider
provider: "API")
Sample Request – Custom API Connection - Existing Provider
provider: "API")
Sample Request – OpenAI Connection
provider: "Open AI")
Sample Request – Azure OpenAI Connection
provider: "Azure Open AI")
Sample Request – Anthropic Connection
provider: "Anthropic")
Sample Response
Update Connection
Updates the configuration of an existing connection. Supported only for external provider connections whereprovider is not API.
Path Parameters
Sample Request
Sample Response
Custom API Connection
Custom API connections let you integrate external models by configuring your own API endpoint. You control the endpoint URL, authentication, request payload, and response mappings. This functionality applies only when the provider type is set to API.Connection Types
Custom API connections come in two types: Default Provider- You define the complete request structure from scratch.
- Full control over payload format, variable placeholders, and response parsing.
- Use when integrating with a custom or proprietary API that doesn’t follow standard LLM provider formats.
- Uses an existing provider’s request/response format such as OpenAI, Anthropic, Cohere, or Gemini.
- You only specify the endpoint and which provider format to use.
- Use when integrating with OpenAI-compatible APIs (like Groq, Together AI) or other providers that follow standard formats.
Path Parameters
Partial Update (PATCH)
UsePATCH for quick changes, such as rotating an API key or updating a model name, without sending the entire configuration object. Only the fields you include in the request will be updated.
Sample Request: Default Provider (Updating Endpoint and Headers)
This example shows how to update connections where you define the complete request structure.
API Fields
Sample Request: Existing Provider (Updating Features)
This example shows how to update connections that use standard provider formats (OpenAI, Anthropic, etc.).
API Fields
Full Replace (PUT)
UsePUT when you need to completely reconfigure a connection or when moving a connection status from DRAFT to FINALIZED. You must provide all mandatory fields for the connection type.
Sample Request: Default Provider (Full Payload)
This example shows how to usePUT for a Default Provider connection. You must include the complete configuration, including all prompt variables, payload structure, and output paths.
API Fields
Sample Request: Existing Provider (Full Payload)
This example shows how to usePUT for an Existing Provider connection. You must specify the provider format to use and the LLM capabilities.
API Fields