---
title: "Re-initiate authentication for a connected account (DEPRECATED)"
method: POST
path: "/api/v3/connected_accounts/{nanoid}/refresh"
tags: ["Connected Accounts", "Authentication"]
deprecated: true
---

# Re-initiate authentication for a connected account (DEPRECATED)

`POST /api/v3/connected_accounts/{nanoid}/refresh`

> **Deprecated.**

DEPRECATED: This endpoint re-initiates the authorization flow for a connected account — a developer-triggered reconnection (e.g. to recover a connection whose credentials expired or became invalid), returning a new OAuth redirect URL where applicable. It does NOT perform background credential auto-refresh; the "refresh" name was misleading, which is why the endpoint is deprecated and may be removed in a future release.

## Path parameters

- `nanoid` string, connectedAccountId, required

## Query parameters

- `redirect_url` string, uri

## Request body

- object
  - `redirect_url` string, uri
  - `validate_credentials` boolean — [EXPERIMENTAL] Whether to validate the provided credentials, validates only for API Key Auth scheme

## Response `200`

Successfully refreshed the connected account authentication. For OAuth flows, a new redirect URL is provided.

- object — Response schema for a refreshed connected account authentication
  - `id` string, required — The unique identifier of the connected account
  - `status` 'INITIALIZING' | 'INITIATED' | 'ACTIVE' | 'FAILED' | 'EXPIRED' | 'INACTIVE' | 'REVOKED', required — The current status of the connected account (e.g., active, pending, failed)
  - `redirect_url` string, nullable, required — The URL to which the user should be redirected to complete the authentication process (null for auth schemes that do not require redirection)

## Other responses

- `400` — Bad request - Invalid nanoid format or the account cannot be refreshed in its current state
- `401` — Unauthorized - Authentication failed
- `403` — Forbidden - Insufficient permissions to refresh this connected account
- `404` — Not found - Connected account does not exist or was deleted
- `409` — Conflict - The connection cannot be refreshed because of a permanent attribute (e.g. its auth scheme does not support refresh, such as API_KEY or BEARER_TOKEN)
- `422` — Unprocessable entity - The connection is in an invalid state for refresh (e.g. connection-data validation failed, or the stored connection status is incompatible with reinitiation)
- `500` — Internal server error - Failed to refresh the connected account authentication

---

[API](https://skmtc.net/composiohq/apis/composio-platform-api.md) · [All operations](https://skmtc.net/composiohq/apis/composio-platform-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/composiohq/composio-platform-api/versions/df7478fc8f3b/schema)