Create Connection
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Slug of the workspace the request acts in
120^[a-z0-9]+(?:-[a-z0-9]+)*$Body
Payload for creating an OpenAPI connection.
The connection ties a base URL (where requests are sent) to an
OpenAPI 3.x specification (which is parsed eagerly into a tool list).
Provide either spec_url or spec_content — not both required.
Base URL for API requests, e.g. 'https://api.example.com'. The path may hold '{name}' placeholders filled from url_variables, e.g. 'https://api.telegram.org/bot{token}'.
500Display name for the connection (unique per workspace).
1 - 255Optional MCPAuthConfig UUID for OAuth2 token rotation. When set, tokens are minted/refreshed on the connection's behalf.
Custom HTTP headers attached to every request. Non-safe headers (e.g. Authorization) are stored encrypted in the secret manager.
Query parameters attached to every request, e.g. an API key the upstream takes as '?api_key='. Secret values are stored encrypted in the secret manager.
Optional human-readable summary of what this API exposes.
Inline OpenAPI 3.x spec as a JSON object. Use instead of spec_url when the spec host is unreachable from the API.
URL to an OpenAPI 3.x JSON or YAML spec. The spec is fetched and parsed eagerly at create time so the connection is ready for use.
Secret values for the '{name}' placeholders in the base URL path, one per placeholder. Stored encrypted in the secret manager.
Response
Successful Response