Create Instance Native
CONNECT-A-CAPABILITY FLOW step 1 (MCP-server variant): define the integration here, then install it for the current identity with integration_install. Register an external MCP server (HTTP or SSE transport) owned by the calling identity, mirroring the admin 'Connect MCP server' modal. Creates the registration row only. For an OAuth2 server pass auth_kind='oauth2' (the default) and no secret -- the row is created unauthenticated and the owner completes the OAuth connect flow afterward from the connection's Marketplace page (this is the 'add the row, authorize after' path). Pass oauth_scopes as a space-separated, least-privilege set when the provider advertises scopes; discovery will not widen an explicitly configured set. For a bearer- or header-key-protected server pass auth_kind='bearer' (or 'api_key_header' with auth_header_name) plus the token as plaintext_secret. Use integration_create_from_openapi instead for a REST API described by an OpenAPI spec. Fails with a clear message if a registration with that name already exists or the inputs are invalid. If this looks like a SERVICE integration (the app acting as itself — infra/DB/API-token vendors) on user-OAuth, the response includes a credential_fit_warning. Creation still succeeds; pass credential_fit_override_reason to acknowledge and suppress it. 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.
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
- Auth: none declared
Headers
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 2 revisions of this API.