Charitology datasets as static JSON with source dates, attribution and reuse terms. Build the Diagnosis, the interventions or the open problems into your own app or donation platform.
One fixed Education cluster in Afghanistan’s 2024 humanitarian plan: exact reported USD requirements/funding, source strings, blank/zero distinctions and provenance. Not independently measured need, final spending or a charity rating.
Fixed 2025 OCHA FTS country-plan-year source rows, reported USD funding, plan requirements, missingness and exact-rational coverage. Not global charitable giving, independently measured need or a ranking.
Complete fixed Disaster Desk edition: attributed reports, exact source versions, status scopes and explicit limitations. Not live or a worldwide needs census.
Version-pinned exact source tokens, decimals, periods, definitions, source rights and explicit coverage. Draft source transcription; no ranking or impact estimate.
Explicit country-window, consolidated-group and selected humanitarian plan-cluster coverage, including source-null, source-empty and uncollected states, linked to exact observations and source rights in the same edition.
Fixed public capture metadata and registry hash. The endpoint wrapper generated date is build metadata; each edition retains its own capture/source dates. No private proposal or subscriber data.
Pinned public source versions, editorial corrections and recorded review declarations; no private local workspaces or automatic scientific qualification.
Explicit as-of research progress: present states, dated editorial corrections, recorded decisions and support limits; unknown historical baseline stays unknown.
Sources in Charitology's bibliography, with the pages that cite them; wider literature coverage is unknown.
Example
const res = await fetch('https://charitology.com/api/v1/conditions.json');
const { data } = await res.json();
console.log(data.map((c) => c.title));
Common responses have the shape { name, description, license, generated, data }.
Fixed Disaster Desk responses use { name, license, generated, data }, with the exact capture instant in generated.
Dataset descriptions remain in the index. The index of available endpoints
is at /api/v1/index.json.
Charitology's schema and editorial material use CC BY 4.0. External data and
documents retain their own terms and attribution. Read each response's
license statement and source rights; the API does not grant new rights in
third-party material. The observations endpoints retain exact source dates,
definitions and missing coverage. A build date does not establish freshness.
How it works
The API is a set of JSON files generated with the site. There are no application keys or accounts. The static host’s request limits and logging policies still apply. Source dates and fixed edition identities describe the data; a build date does not establish its freshness.
License
Charitology’s schema and editorial material use Creative Commons Attribution 4.0. Cite them as “Charitology (charitology.org)”. External data and documents retain their own source-specific terms, attribution and exceptions. Each response states its scope; the observations endpoints also retain individual source rights. This notice does not grant new rights in a publisher’s data or financial document.
Why an API
Most giving decisions happen somewhere else: on donation platforms, in workplace giving portals and in advisors’ spreadsheets. An open API lets the method travel to where decisions are made, which helps the system coordinate instead of fragmenting further. See the Fragmentation Problem.