Public API

API documentation

The open-data routes return OC4IDS project package JSON for reuse, validation and archiving. The dashboard routes remain available for portal interface data, but they are not the standards publication surface.

Method

Endpoint

Use

GET

/opendata/projects.json

Bulk machine-readable project package for all currently published infrastructure projects.

GET

/opendata/projects.csv

Flat project table derived from the OC4IDS project package for spreadsheet and BI tools.

GET

/opendata/projects.xlsx

Excel workbook containing the same flat project table as the CSV endpoint.

GET

/opendata/projects.flat.xlsx

Multi-sheet Excel workbook flattening the entire OC4IDS package: one sheet per repeating element (projects, parties, contracting processes, documents, milestones, and more), each child row keyed back to project_id.

GET

/opendata/projects/{id}

Stable JSON URL pattern for one project. Replace {id} with the numeric project reference shown on the portal.

GET

/api/projects

Portal-shaped API used by the dashboard. Prefer the /opendata routes for standards publication.

GET

/api/projects/{id}

Portal-shaped project detail API used by the project pages.

Stable project JSON URL pattern

Project package URLs use the numeric project id from the portal.

https://infrastructuretransparencyzambia.org/opendata/projects/{id}

Example: /opendata/projects/1

Validation workflow

Use the OC4IDS Data Review Tool Link tab with the bulk package URL or a single-project package URL.

Open Data Review Tool Open data page