Skip to main content
POST
ConnectIntegrationAPI mirrors the erdo_connect_integration MCP tool.

Authorizations

Authorization
string
header
required

An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

Body

application/json
app
string
credentials
Credentials is caller-supplied secret material (DB passwords, API keys, · object

service-account JSON). encore:"sensitive" keeps it out of request trace storage — the same treatment integration.CreateIntegrationRequest.Credentials gets.

managed_access
string

manages. It is honoured only on the native credential path: a Pipedream connection is not an integration row this column lives on, and an OAuth grant is a named person's account at the provider, which is never something to spend on another business's behalf. Both are refused rather than ignored — a caller who asked for lending and got silence would believe its clients could use the key.

It carries no jsonschema tag and handleConnectIntegration clears it before the logic runs, so no MCP caller can set it whatever the schema generator does with an untagged field: widening which organizations a credential serves is not a decision a model should be able to take, the same reasoning that keeps manager-key minting off MCP.

name
string
return_url
string

authorization at connect_url. Only meaningful for OAuth apps (native OAuth and Pipedream) that hand back a connect_url. Empty returns the user to Erdo's data page — the default for MCP/CLI callers with no product origin of their own; a portal built on /v1 passes its own page so the operator lands back on it. Must be an absolute http(s) URL with no embedded credentials.

rotate_credentials
boolean

instead of adding a second one. A rotated key must land on the connection everything else already references — a sibling connection leaves every pinned widget, automation and shared grant pointing at the dead key.

scopes
string[]
share_with_org
boolean

instead of the default private-to-the-connector. A credential connected headlessly is usually org infrastructure (a customer org's calendar, a shared SaaS key) that teammates and org agents must be able to see and build on — private-by-default is right for a personal OAuth grant, wrong for that.

Response

Success response

app
string
connect_url
string
integration_id
string
next_step
string
organization_name
string
organization_slug
string
status
string