---
title: "List Connector Readiness Checks Endpoint"
method: GET
path: "/v1/connectors/{connector_id}/readiness-checks"
tags: ["v1-connectors"]
---

# List Connector Readiness Checks Endpoint

`GET /v1/connectors/{connector_id}/readiness-checks`

List ARD-720 post-snapshot validation evidence for this connector.

Returns the append-only paper trail of per-table checks the engine-setup
gate emitted on each attempt. The schema's
``branch_readiness_checks_select_policy`` enforces RLS via
``current_user_accessible_connectors`` — callers see only the rows for
connectors they have read access to.

A connector that's stuck in ``failed_validation`` will surface its
failing rows here (combine with ``?only_failed=true``); customers use
this to understand why their branch isn't routing without needing
operator intervention.

## Path parameters

- `connector_id` string, required

## Query parameters

- `attempt_id` string, nullable
- `check_name` string, nullable
- `only_failed` boolean
- `limit` integer
- `offset` integer

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/tryardent/apis/fastapi.md) · [All operations](https://skmtc.net/tryardent/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tryardent/fastapi/versions/f92d8d54bae2/schema)
