---
title: "Cluster Feedback"
method: GET
path: "/v1/entities/feedback/clusters"
tags: ["entities"]
---

# Cluster Feedback

`GET /v1/entities/feedback/clusters`

## Request

- Base URL: `https://api.bitpoort.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.bitpoort.com/v1/entities/feedback/clusters`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Flywheel item 3 — the loop back to clustering quality.

Exposes what analysts DECIDED about cluster proposals so the clustering
engine can consume its own report card: ``rejected`` cluster refs are a
down-weight signal, ``accepted`` a positive one, and split/detach ops from
the append-only audit log are direct over-merge corrections. Read-only;
the engine (or an analyst) drives what to do with it.

## Query parameters

- `status` string, nullable
- `limit` integer

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/bitpoort/apis/bitpoort-api.md) · [All operations](https://skmtc.dev/bitpoort/apis/bitpoort-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bitpoort/apis/bitpoort-api/revisions/1a51d8566777?raw)