---
search:
  tags:
    - Connected accounts
    - POST
seo:
  description: >-
    Ask the provider whether a connected account still works, and… Reference for
    the POST /api/v2/connections/{secretName}/check endpoint in the Anlyon API.
sidebar:
  label: Check a connected account
  badge: POST
title: Check a connected account
type: openapi-operation
---
Ask the provider whether a connected account still works, and record the answer on the secret's `health`. The same call for both kinds: an API key is sent once, in the integration's own header, to its one read-only check URL; a signed-in account is asked for from the connector service with a forced refresh, so the provider itself says whether the grant is still honoured. The credential is never returned. An account that does not work is an answer, not an error: the call answers `200` with `health.status: needs_reauth` and a `reason`, and the next dispatch that uses it fails before anything is sent. Only a check that could not be made is an error (`CONNECTION_KEY_CHECK_FAILED` or `CONNECTION_PROVIDER_ERROR`), and it leaves `health` unchanged. A secret you stored directly cannot be checked (`400`). Counts toward the same limit of 10 per minute per workspace as connect sessions. Anlyon also runs this check on its own, once a day per account and after a dispatch the provider answers 401.

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