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. The completed outcome and check time are retained on that connection as lastCheck, including failed checks. 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
Headers
Path Parameters
Response
OK
True only when the connection is active at the provider, a scoped token was successfully minted during this probe, and, for a provider that also checks that token against its vendor, the vendor did not refuse it. 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.