VOvoidly
Censorship Data

Snapshot of what Voidly measures (block counts under review)

Changed on

Under 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. Coverage fields remain (countries_measured, measurement_networks, domains_measured, domains_categorized, category_coverage_pct, freshest_measurement_utc); countries_with_confirmed_blocks, confirmed_block_pairs, deepest_censor and most_blocked_category are null while held.

get/v1/measurement/summary

Request

  • Base URL
    https://api.voidly.ai
  • URL
    https://api.voidly.ai/v1/measurement/summary
  • Auth
    none required

Response

schema voidly-censorship-summary/v1: { countries_measured, countries_with_confirmed_blocks, confirmed_block_pairs, deepest_censor {country, domains_blocked}, most_blocked_category {code, countries}, measurement_networks, domains_measured, domains_categorized, category_coverage_pct, freshest_measurement_utc, see_also, methodology, generated_at }

Changes