SetIntegrationIdentityAPI writes a connection's stored account identity
(account_id, and for Google Ads agency connections the manager/MCC login_customer_id) into its encrypted credentials, leaving every other credential key untouched, and returns the integration’s summary in the GET /v1/integrations shape — never any token material.
This is the escape hatch the OAuth callback’s auto-detection defers to: the detector only stamps login_customer_id when a fresh token’s sole accessible account is a manager, and every ambiguous shape needs the id set explicitly afterwards. The internal UpdateIntegration surface that used to be the documented way to do that is session-only, so a /v1 consumer had no way to set the id a manager connection hard-requires (client-account requests, managed-container provisioning) or to backfill account_id onto connections that predate identity stamping.
Authorizations
An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).
Path Parameters
Response
Success response
when the upstream provider last refused this connection's credential. Status cannot carry it: a retired key leaves a connection 'connected' here because Pipedream signs calls with it quite happily and simply returns the provider's 401 — which is how a widget on a customer's live site went two and a half days without anyone noticing. Reported, never acted on.

