Open Data & OCDS Export

Machine-readable records in open contracting standards

Standards

PisoScan publishes each record in the formats that BetterGov's OpenGovChain uses for its procurement and infrastructure modules: the Open Contracting Data Standard (OCDS 1.1) and the Open Contracting for Infrastructure Data Standard (OC4IDS). OpenGovChain is marked pre-launch in its repository, so PisoScan does not read from or write to that chain. The exports are ready for it, or for any OCDS tool.

Endpoints

OCDS release package for a contract award

GET /api/ocds/award/{recordId}

Example: /api/ocds/award/09d4cdac28c3599e7d170375

OC4IDS project package for a DPWH contract

GET /api/oc4ids/project/{contractId}

Example: /api/oc4ids/project/26K00001

Verifying a record

Every award and project page has a Source record tab showing the exact line that was hashed. To check it yourself:

printf '%s' '<hashed input from the page>' | sha256sum
# the first 24 characters must equal the award's record ID

The hashed line is the source row as JSON: ["philgeps", reference, contractNo, title, awardee, organization, area, amount, awardDate, orgLevel, prov, mun, brgy], or ["dpwh", …] with the DPWH columns in source order. Identical duplicate rows get a trailing counter.

Upstream data

Budget: Philippine Budget Data API (GAA, NEP, budget cycle, hearings). PisoScan stores a snapshot made with npm run fetch:budget.
Procurement: Open PhilGEPS data (CC0).
Infrastructure: DPWH contract list via BetterGov.ph.