---
search:
  tags:
    - Connected accounts
    - POST
seo:
  description: >-
    Make a connected account work again, the way it was connected.… Reference
    for the POST /api/v2/connections/{secretName}/reconnect endpoint in the
    Anlyon API.
sidebar:
  label: Reconnect a connected account
  badge: POST
title: Reconnect a connected account
type: openapi-operation
---
Make a connected account work again, the way it was connected. The secret keeps its name, its hosts and its placement, so nothing that references `{{secret:NAME}}` changes. For an API-key integration, send the new key as `apiKey`: Anlyon checks it with the provider the way it checked the first one, replaces the stored value, and answers `status: completed` with the secret. A key the provider refuses changes nothing (`CONNECTION_KEY_REJECTED`). For a sign-in integration, send an empty body: Anlyon starts a consent session for the account's existing connection and answers `status: pending` with the `session`. Open its `connectUrl` or hand its `consent` values to the console's window, then call `POST /api/v2/connections/sessions/{sessionId}/complete` as for a first connect; completing marks the account working again. Sending a key for a sign-in account, or none for a key account, is `400`. Counts toward the same limit of 10 per minute per workspace as connect sessions.

`POST /api/v2/connections/{secretName}/reconnect`