---
title: "Reconnect an Integration"
method: POST
path: "/api/platform/v1/connections/{id}/reconnect"
tags: ["data"]
---

# Reconnect an Integration

`POST /api/platform/v1/connections/{id}/reconnect`

## Request

- Base URL: `https://docs.amdahl.ai`
- URL: `https://docs.amdahl.ai/api/platform/v1/connections/{id}/reconnect`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Restore a connection stuck in an error or needs-reauth state, in place on the existing data source so its sync history and id survive (no duplicate row). Use when a user clicks reconnect on a broken connection: an OAuth provider returns a fresh authorize URL to redirect through, an api_key connector takes a replacement key, and a tracked social handle simply re-triggers its sync. A non-existent or cross-tenant id is a clean not-found.

## Path parameters

- `id` string, required: UUID of the connection to reconnect.

## Request body

- object
  - `api_key` string: For api_key connectors: the replacement API key / token to store (encrypted) on the existing source. Ignored for oauth and social-handle connectors.
  - `api_id` string: For an api_key connector whose credential is a PAIR (today only Aircall): the non-secret id half, re-stored alongside the replacement token. Required when the catalog entry asks for it.
  - `return_to` string: For oauth connectors: console URL to redirect back to after the re-handshake (first-party origins only).

## Response `200`

OK

- object
  - `data` unknown

## Other responses

- `400`: Invalid input - failed schema validation
- `401`: Authentication required
- `403`: Forbidden - missing scope or role
- `500`: Internal server error

---

[API](https://skmtc.dev/amdahl/apis/amdahl-platform-api.md) · [All operations](https://skmtc.dev/amdahl/apis/amdahl-platform-api/llms.txt) · [OpenAPI document](https://skmtc.dev/amdahl/apis/amdahl-platform-api/revisions/d4eee33e2472?raw)