Refresh connection credentials
Forces Elaichi to mint a fresh access token for this connection in place. Use it for maintenance on a connection that is still healthy; reconnect is the repair for one that is not. No body. Same permission as reconnect, and only meaningful on a bound, active row whose authentication_method is refreshable (oauth2, oauth2_client_credentials, jwt_bearer), which is what the row's can_refresh_credentials reports. Everything else answers 409: not_refreshable (no provider call is made), needs_reauth (the provider rejected the refresh; the row is set to needs_reauth before this reply), or connection_disconnected. The 200 is a receipt, never the credential itself.
Request
- Base URL: https://api.elaichi.ai
- URL: https://api.elaichi.ai/connection/{id}/refresh-credentials
- 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.
Response
OK
Changes
No recorded changes to this operation across all 1 revision of this API.