Measurement and domain coverage (block counts under review)
Changed onUnder review: while the block-verdict review is on, this route answers HTTP 200 with every verdict field set to unknown or null (some coverage fields may remain), a top-level review object (status under_review, verdict unknown, reason, source, and dataAsOf: the data date, or null when the source reports none or could not be read) and X-Voidly-Verdict-Review: under_review, with Cache-Control no-store. A held answer is not an outage and not a finding either way; see https://voidly.ai/data-quality#block-verdict-review. While held, the block and accessible record counts are null, coverage counts may be null, and confirmed_block_layer gives the layer window. The example shows the held shape with illustrative values; do not interpret it as current data.
Request
- Base URLhttps://api.voidly.ai
- URLhttps://api.voidly.ai/v1/atlas/coverage
- Authnone declared
Response
Source-grounded synthetic contract example; illustrative values are not a live receipt.
Changes
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info
- breaking
the response property
became nullable for the status - breaking
the response property
became nullable for the status - breaking
the response property
became nullable for the status - breaking
the response property
became nullable for the status - breaking
the response property
became nullable for the status - breaking
the response property
became nullable for the status - breaking
the response property
became nullable for the status - breaking
the response property
became nullable for the status - info
added the optional property
to the response with the status
- breaking