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

# Test Connection

> Check whether a connection's authorization is still valid.

Oviond checks the health of each connection's token automatically. A daily auth-test pings each platform with the stored credentials, and the OAuth refresher updates the status when a token refresh fails. You don't run a manual test in the app — instead, each connection shows a status badge:

* **Token Valid** — the token is authorized and data should flow.
* **Token Expired** — the token has expired or been revoked; refresh it.

You'll see this badge on the **Data Sources** tab in a client's project and in **Settings → Data sources** (where it appears as **Token valid** / **Token expired**, and you can filter the table by status).

## Where to look

* A widget shows a data error and you want to know whether re-authorization is needed.
* You just refreshed a connection and want to confirm it's working.
* You're debugging a report that depends on a specific connection.

In each case, open the connection in the **Data Sources** tab or in **Settings → Data sources** and read its status badge.

## If a connection shows Token Expired

1. Click **Refresh** (project tab) or **Refresh token** (Settings) to start a fresh OAuth flow. Your account selection is preserved.
2. Complete the OAuth flow with the same login. The badge returns to **Token Valid**.
3. If refresh doesn't resolve it, the authorizing user's access in the source platform may have been revoked — check the platform's admin for the token's status.

<Note>
  The API exposes a `POST /v1/datasources/test` endpoint that takes an `auth_id` and returns `{ connected, message }`, plus `POST /v1/data/test` to test a connection against the data service. See the API reference for details.
</Note>