API Docs — OpenCourts.FYI

Machine-readable access (mock)

These examples demonstrate how CKAN APIs and DCAT feeds will look in the real system. In this mock site, the endpoints are static JSON files.

CKAN Action API (examples)

/api/3/action/package_list
/api/3/action/package_show?id=nc-criminal-dispositions-2024
/api/3/action/package_show?id=sc-civil-docket-events-2024
/api/3/action/package_show?id=nc-probate-estates-2023

DCAT catalog (example)

In production this is provided by ckanext-dcat.

/api/dcat_catalog.json

Code samples

Fetch dataset metadata (Action API):

curl -s \
  https://opencourts.fyi/api/ckan/package_show_nc_criminal.json \
  | jq .result.title

Canonical mock portal: opencourts.fyi (custom domain). The GitHub Pages project URL is non-canonical and may not support all root-relative links.

Schema / field dictionaries

Machine readability depends on field dictionaries: name, type, description, constraints. In CKAN this is typically stored in metadata fields or DataStore schema and surfaced on dataset pages.