evidoria

API

Evidoria's REST API is open for reading: every published practice, catalogue, organisation and the knowledge-map ontology, in JSON (plus GeoJSON and SKOS). Content is licensed CC-BY-4.0 — reuse it with attribution.

Endpoints

EndpointWhat it returns
GET /api/v1/practices/Published practices. Filters: type, scale, country, catalogue__slug, needs_enrichment; plus search and ordering (score, created_at, updated_at, title).
GET /api/v1/practices/<slug>/One practice in full: sections, key results, evaluation profile, dossier, sources, persistent ID.
GET /api/v1/practices/geojson/FeatureCollection of the filtered practices that have coordinates.
GET /api/v1/practices/adoptions/geojson/Geolocated adoptions (the replication graph).
GET /api/v1/practices/transferable/Practices ranked by transferability to your context (country, governance_type, scale, income_level, budget_band, horizon_band, need_text).
GET /api/v1/evaluations/The evaluations table in bulk: one row per evaluation with nested criterion scores and justifications. Filters: catalogue, practice, is_final, evidence_strength. Requires a free API key (create one in your workspace); per-practice evaluations on the practice detail endpoint stay public.
GET /browse/export.csvCSV of any browse filter set (same query params as the Browse page; capped at 5 000 rows).
GET /api/v1/catalogues/Public catalogues (tenants) with rubric metadata and languages.
GET /api/v1/organisations/Organisations behind the practices.
GET /api/v1/taxonomy-schemes/Per-catalogue facet vocabularies.
GET /api/v1/dcat/DCAT-AP catalogue description (JSON-LD) for open-data harvesters; one dataset per public catalogue with CSV + JSON distributions.
GET /api/v1/ontology/The canonical knowledge map (pillars → themes → topics, with counts).
GET /api/v1/ontology/skos/The same ontology as SKOS/JSON-LD (EuroVoc/SDG mappings included).
POST /api/v1/copilot/Grounded, citing, abstaining copilot answer for {"query": "…"} (throttled: 20/hour).
POST /api/v1/auth/token/Token exchange for password accounts; magic-link users create/revoke their personal key in the workspace. Send it as Authorization: Token <key>.
POST /api/v1/ingest/practices · GET /api/v1/ingest/cataloguesEditor-token growth ingest and its discovery endpoint.

Try it