Introduction

Mission

OpenNG collects, validates, and publishes Nigerian public data—fuel, holidays, geography, and more—as stable JSON behind a single API surface. The goal is to replace brittle PDF scraping with something you can call from any stack and trust in production.

Who uses OpenNG

Product builders

Dashboards and internal tools

Teams wire OpenNG into BI tools, internal portals, and ops dashboards where fresh numbers beat static spreadsheets.

Research and journalism

Analysts and reporters use filters and exports to compare periods, states, and categories without maintaining one-off scrapers.

Platform operators

If you run civic infrastructure, OpenNG is meant to sit beside your own services: cache aggressively, respect rate limits, and fall back to documented error codes when something drifts.

How data reaches you

Ingest

Imports land in staging with batch identifiers. Scrapers and manual pipelines write rows there first—never straight to the public tables the API reads.

Validate

Stored procedures score each batch: required fields, referential integrity against ref tables, and domain rules (for example valid holiday calendars).

Serve

Validated rows migrate to public schema tables. The API reads only from public and ref, so what you see in /v1 matches what passed validation.

What to read first

Start with Getting started for base URL and first requests, then Authentication, Response format, and API conventions before you open dataset pages.

Dataset snapshot

Live and planned resources follow the same ResourceFactory contract: list, meta, detail, and export where policy allows.