Create Instance From Openapi
CONNECT-A-CAPABILITY FLOW step 1 (REST/OpenAPI variant): define the integration here, then install it for the current identity with integration_install. Add a new REST 'connected tool' (MCP integration) owned by the calling identity, built from an OpenAPI spec URL. thinqOS fetches the spec, generates the tool manifest, encrypts any provided secret server-side, and probes the upstream. Mirrors the Connected Tools screen's 'Import from OpenAPI' flow. For a secured API pass the bearer/API key as plaintext_secret (never stored in the clear). Fails with a clear message if the spec is unreachable, the manifest is invalid, or a registration with that name already exists. connection_mode is required, no default: pass 'shared' (one credential the whole folder uses) or 'per_caller' (each identity connects and uses their own credential) — you must always pick one. For a secured spec (bearer or API-key auth) with no secret available yet -- e.g. building a public Discover template without pasting your own production key -- pass allow_unconnected=True to create the row unauthenticated; the auth scheme is still recorded and the installer supplies their own credential at connect time. Omitting both a secret and allow_unconnected=True fails with a clear error rather than silently creating an unusable row.
Request
- Base URL: https://app.thinqos.com (the document declares no server; this is the origin it was published from)
- URL: https://app.thinqos.com/api/integrations/instances/from-openapi
- Auth: none declared
Headers
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 2 revisions of this API.