---
title: "Get Requirement Summaries"
method: GET
path: "/marketing/requirement-coverage/requirements"
tags: ["marketing-requirement-coverage"]
---

# Get Requirement Summaries

`GET /marketing/requirement-coverage/requirements`

Per requirement: how often it has been checked, how it came out, and what reviewers said.

One grouped query for a whole page of the library. The per-requirement route below answers the
same question in full, with the collateral listed; this one is what a list can afford to ask.

Requirements with no checks are **omitted** rather than returned as zeros. A row shows this strip
only when there is something to say, so a caller keying a map on the response gets `undefined`
for exactly the rows that should render nothing.

## Query parameters

- `requirement_id` string[], required

## Response `200`

Successful Response

- RequirementCoverageSummary[]
  - `requirement_id` string, uuid, required
  - `collateral_checked` integer
  - `counts` CoverageOutcomeCounts — The three ways a checked requirement can come out, never folded into two. `not_determined` is on the wire beside the other two rather than added into either, because a panel that reports "31 passed" while ten of them were rules the model could not judge from what the collateral shows is making a claim nobody measured — and the whole point of this surface is to be believable.
    - `passed` integer
    - `failed` integer
    - `not_determined` integer
  - `confirmed` integer
  - `false_positive` integer

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/kobaltlabs/apis/fastapi.md) · [All operations](https://skmtc.dev/kobaltlabs/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/kobaltlabs/fastapi/revisions/425d5b8a3c17/schema)