Reconnect Instance
Needs-attention repair: re-probe, report, and preserve every access grant.
What this does NOT do is the point (TOS-2708): it never deletes the connection row, never touches folder membership, never drops a resource binding, and never clears a stored token. It re-runs the same probe the Test button runs — which may resolve the problem outright when the cause was transient (a rate limit, a service blip) — recomputes the per-tool rollup, and returns the specific next action plus the grants that survived.
When the credential genuinely has to be re-authorized, the browser OAuth flow at reauthorize_path UPSERTS onto this same connection row (_record_oauth_login_tokens), which is what makes the preservation guarantee true rather than aspirational.
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/{instance_id}/reconnect
- Auth: none declared
Path parameters
Headers
Response
Successful Response
Changes
No recorded changes to this operation across all 3 revisions of this API.