Reconnect connection
Mints a fresh connect_url for an existing connection; this is the fix for needs_reauth. The connection id and every toolbox entry pinned to it survive, so nothing has to be rebuilt. The new account replaces the old binding and the old stored credential is dropped. The body is optional: an empty POST returns the person to the app root. On an org-owned connector it needs the same use level as POST /connection (403 connector_not_shared once the share was withdrawn). 409 reconnect_not_needed when the connector is a remote MCP server with no sign-in (auth mode none) and the connection is active: there is nothing to reconnect, and the row's can_reconnect is false for the same reason. A pending no-sign-in connection (tab closed before the callback) still reconnects; it is the only way to a fresh session.
Request
- Base URL: https://api.elaichi.ai
- URL: https://api.elaichi.ai/connection/{id}/reconnect
- Auth: HTTP bearer
Path parameters
Connection id (conn_…).
Headers
Target organization (org_…). Required for cookie/session auth on org-scoped routes; optional for API tokens, which carry their organization, and rejected when it names a different one.
Request body
Response
OK
Changes
No recorded changes to this operation across all 1 revision of this API.