---
title: "Which sources could check each verification field"
method: GET
path: "/api/end_users/verification/coverage"
tags: ["EndUsers"]
---

# Which sources could check each verification field

`GET /api/end_users/verification/coverage`

## Request

- Base URL: `https://app.herondata.io`
- URL: `https://app.herondata.io/api/end_users/verification/coverage`
- Auth: API key in header `x-api-key`

Get, for every field the verification response carries, the sources that could check it, best authority first. A constant rather than a fact about one submission: it says what the product can verify at all, which is why it takes no end user.
A channel the submission stated through is never one of them. The form, the customer's own rows and the broker's submission are the claim under check, so they appear on a field's check with their value and nowhere here. An empty list means no run can ever verify that field.

## Response `200`

OK

- CoverageResponseSchema
  - `fields` object: Per field, the sources outside the deal whose reports state it, best authority first, keyed as the verification response keys the field (an owner's as `owner.ssn`). Empty where no source states the field, so nothing can compare it against the claim.

## Other responses

- `404`: Verification is not enabled for this account

## Changes

- **2026-11-03** `bd8008e49534`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/herondata/apis/heron-data-api/changes/api/end_users/verification/coverage/get.md)

---

[API](https://skmtc.dev/herondata/apis/heron-data-api.md) - [All operations](https://skmtc.dev/herondata/apis/heron-data-api/llms.txt) - [OpenAPI document](https://skmtc.dev/herondata/apis/heron-data-api/revisions/1ec936e17fef?raw)