Check a connection against the provider and try minting a token
Checks a connection against the provider and tries to mint a short-lived access token, returning what the provider reported. A suspended or revoked installation is still HTTP 200 with ok=false, so read that field rather than the status code. For a directly registered connection in the pending state this is also the activation step: the probe performs a fresh mint through the trust the customer granted and, if it succeeds, moves the connection to active and reports activated=true; until then it stays pending and the failure text is the bounded “delegate trust is not active”.
Authorizations
A Recursion API key, created in the console under API keys.
Headers
Optional tenant consistency check. When present, it must name the tenant bound to the API key, including when x-organization-id is default.
1Organization in which to act. Required for a tenant-scoped API key. Optional for an organization-scoped key, where it must name that same organization. The value may be an organization id or default.
1Path Parameters
Integration connection id (UUID) as returned by managedAgentsListIntegrationConnections.
Response
Result of a live health check against one integration connection: its refreshed state at the provider, whether a token could be minted, and what is missing if not. A failed check is reported here rather than as an HTTP error.
Result of a live health check against one integration connection: its refreshed state at the provider, whether a token could be minted, and what is missing if not. A failed check is reported here rather than as an HTTP error.
True only when the connection is active at the provider and a scoped token was successfully minted during this probe. False means the connection cannot currently be used; read failure for why. A probe that fails this way is still an HTTP 200.
Number of provider resources the connection can authorize, for example selected GitHub repositories. The live probe credential may be narrower when the provider cannot represent the entire connection scope in one token. Zero when no token could be minted.
-9007199254740991 <= x <= 9007199254740991Lifecycle of the connection as of this probe: pending (registered, waiting for the customer to grant trust), active (usable), suspended (paused at the provider), or revoked (uninstalled or deleted). Refreshed here, so it can differ from the previously stored value: a pending connection whose trust proved usable is reported active.
Whether a scoped credential could actually be issued during this probe. This is the check that predicts whether a session using the connection will work.
True when this probe moved a pending connection to active by proving its trust with a successful mint. Omitted (false) on every later probe of the same connection.
GitHub installation permissions above the launch App contract. Reported, not enforced: reduce the App permissions in GitHub and have installation owners approve the update.
Human-readable reason the probe did not succeed, such as a suspended install or a rejected mint. Empty when ok is true.
Permissions this service requires that the install has not granted at the required level. Reported, not enforced: accept the provider's pending permission request to clear them.