Skip to main content

ng-postcode

Python library for Nigeria's National Digital Alphanumeric Postcode System (NDAPS), the building-level postcode NIPOST launched in October 2026. Parse, validate and format postcodes offline, and call the postcode.gov.ng API for lookup, autocomplete and reverse geocoding.

Also available for Rust as ng-postcode on crates.io for JavaScript as ng-postcode-js on npm, and for Java as ng-postcode-api on Maven Central.

pip install ng-postcode            # offline core, no dependencies
pip install "ng-postcode[client]"  # adds the API client (httpx)

Format

An 11-character code in five segments: state, LGA, district, area, building unit.

Form Example Use it to
Canonical EK-01-A03-FK-01 Write a code and pass it between systems
Spaced EK 01 A03 FK 01 Show a code to people
Compact EK01A03FK01 Store and compare codes

Compact form as a regular expression: ^[A-Z]{2}(0[1-9]|[1-9][0-9])[A-Z0-9]{3}[A-Z]{2}(0[1-9]|[1-9][0-9])$

Offline

Expected failures are returned as values, so the type checker makes you handle them.

from ng_postcode import Postcode, Segment, parse

match parse("ek 01 a03 fk 01"):
    case Postcode() as code:
        print(code)  # EK-01-A03-FK-01
        print(code.compact)  # EK01A03FK01, store this
        print(code.spaced)  # EK 01 A03 FK 01
        print(code.prefix(Segment.AREA))  # EK-01-A03-FK
    case error:
        print(error)  # e.g. "invalid lga segment"
  • parse accepts hyphenated, spaced or compact input in either case.
  • parse_lenient first swaps look-alikes that cannot occur where they stand (O/0, I/1, S/5, B/8) and reports how many it changed.
  • from_segments assembles a code from its parts and zero-fills the LGA and unit.
  • parse_prefix reads a code cut off after a segment, such as the district EK-01-A03, and Postcode.truncate cuts a code down to one. A prefix knows which codes it contains, so it groups them by state, LGA, district, or area.
  • Postcode is immutable, hashable and sorts by state, LGA, district, area, unit.

A well-formed code is not necessarily assigned to a building. Only the API can confirm that a postcode exists.

Convert a CSV file

The package installs an ng-postcode command that checks a column of postcodes and writes the file back with four columns added.

ng-postcode orders.csv --column postcode --out checked.csv
id,postcode,postcode_compact,postcode_status,postcode_suggestion,postcode_error
1,ek 01 a03 fk 01,EK01A03FK01,valid,,
2,EK-O1-A03-FK-01,,suggested,EK-01-A03-FK-01,invalid lga segment
3,360001,,invalid,,"expected 11 letters and digits, found 6"
4,,,empty,,
  • valid rows carry the compact code to store.
  • suggested rows only parse after look-alike characters are swapped. The fix is offered for a person to confirm, and the compact column is left empty.
  • invalid rows say what is wrong, and empty rows had no value.

It works offline and reads one row at a time, so the size of the file does not matter. Add --confirm to ask NIPOST whether each well-formed code is assigned to a building. That needs pip install "ng-postcode[client]" and your own key in NG_POSTCODE_API_KEY, makes one free level 1 lookup for each distinct code, and adds a postcode_assigned column.

API

from ng_postcode import Postcode, parse
from ng_postcode.api import ApiError, lookup
from ng_postcode.client import Client, TransportError

code = parse("FC-03-B06-AG-12")
assert isinstance(code, Postcode)

with Client(api_key="nipost_live_...") as client:
    found = client.send(lookup(code, level=1))

match found:
    case ApiError() | TransportError():
        print(found)  # e.g. "invalid_api_key (401): ..."
    case _:
        print(found.valid, found.status)  # True valid

send returns the typed response, an ApiError (for example auth_required or insufficient_credits) or a TransportError. AsyncClient has the same interface for asyncio.

ng_postcode.api covers lookup, autocomplete, reverse geocoding and nearby search. Each function returns a Request value and decode turns a status and body into a typed result, so it works with any HTTP client without the client extra.

Get a key from the NIPOST developer dashboard. Level 1 lookups confirm a code is assigned; levels 2 and up return address details and consume credits.

License

MIT

Metadata

Release files for ng-postcode 0.3.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ng-postcode 0.3.3
File Size Uploaded
ng_postcode-0.3.3.tar.gz 22.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ng-postcode 0.3.3
File Interpreter ABI Platform
ng_postcode-0.3.3-py3-none-any.whl Python 3 none any Details

Total release size: 39.9 kB

Release files / ng_postcode-0.3.3.tar.gz

Download URL ng_postcode-0.3.3.tar.gz
Size 22.4 kB
Tags Source
SHA-256 checksum
How to use checksums
44f96676230d152577f946f3b6e8e094f543dd777a51228b2e6ac0750fc2c41f
BLAKE2b-256 checksum
How to use checksums
fd53ecd99d02d23847521e3949e72d1255e7f0cfa3f9150b701d9c2b38445033
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / ng_postcode-0.3.3-py3-none-any.whl

Download URL ng_postcode-0.3.3-py3-none-any.whl
Size 17.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
aea575aaf851c3848580be1222d46f17e1951fef840c045634c89f1533eb8763
BLAKE2b-256 checksum
How to use checksums
4063ad9c637c6e341edbd07a50af896996b2612d900527da3840c6ffd3d7ab1c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.5

2 release files

0.3.4

2 release files

This release

0.3.3 This release

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page