> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chift.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring & Updating Connections

This guide explains how to monitor the status of existing connections and how to update them if needed.\
It is intended for developers managing consumer connections in Chift.

## Monitor connection status

Once the activation link has been shared, you need to verify whether the connection was successfully established. There are several options:

#### 1. Webhook

Subscribe to the `account.connection.created` event.\
Triggered automatically when the connection becomes active.

> ⚠️ **Important:**\
> The `account.connection.created` webhook is only triggered when the connection has been successfully created.\
> If the consumer never completes the activation, **no webhook event will be sent**.\
> We therefore recommend combining this with another logic — for example, a timeout or periodic check — to handle incomplete activations.

[Webhook Docs ↗️](https://docs.chift.eu/developer-guides/webhooks#list-of-events)

#### 2. API call

Retrieve all connections linked to a consumer and check their `active` status.

**Endpoint:** `Get connections`\
[API Reference ↗️](https://docs.chift.eu/api-reference/endpoints/connections/get-connections)

**Required field:**

* `consumerId` — From the consumer creation step

#### 3. Redirect URL parameters

If a `redirect_url` was set when creating the consumer, Chift automatically appends query parameters when the user is redirected after activation.

**Returned parameters:**

* `consumerId`
* `connectionId`
* `connectionStatus` (`active` / `inactive`)
* `error` *(only in case of error)*
* `isExpiredError` *(only in case of error)*

More details on the feature and how to activate it: [Configure account ↗️](https://docs.chift.eu/back-office/getting-started/configure-account#redirect-url-parameters)

***

## Update an existing connection

⚠️ **Pro tip:** Do **not** delete and recreate a connection if credentials expire or activation was not completed.\
Instead, use the update endpoint to resend the activation link or adjust metadata (e.g. `name`, `redirect_url`).

**Endpoint:** Update an existing connection\
[API Reference ↗️](https://docs.chift.eu/api-reference/endpoints/connections/update-an-existing-connection)

**Required fields:**

* `consumerId` — From consumer creation
* `connectionId` — From connection creation

> Updating a connection allows you to maintain active links without forcing the user to reconnect from scratch.\
> This preserves historical data and ensures smoother API usage.