This update introduces Postcode Validator and Postcode Autofill for checking postcodes and populating address fields. Portal pricing and billing updates are underway, with navigation connections and logistics routing capabilities coming soon.

Postcode Validator

Postcode Validator checks whether a supplied postcode exists in the National Digital Postcode system. Applications can use the result to accept a recognised postcode or prompt the user to review an unrecognised entry.

Use it to check postcodes during:

• Customer registration and merchant onboarding.
• Address entry and updates.
• Delivery requests.
• Reviews of existing address records.

This gives businesses a check at the point of entry, helping them identify unrecognised postcodes before storing or using them. It also supports checks on records already held in business systems.

A recognised postcode confirms that the location reference exists. It does not establish that a person lives, owns property or operates a business there.

Postcode Autofill

Postcode Autofill retrieves the address and location data associated with a postcode. Applications can use the response to populate corresponding address fields, reducing manual entry and supporting consistent address information across forms and records.

The user experience follows three steps:

1. The user enters a postcode.
2. The application retrieves the associated data and populates the relevant fields.
3. The user reviews and confirms the details.

Use it in registration, onboarding, e-commerce checkout, delivery bookings and address updates. Businesses can incorporate the returned information into the address forms they already use.

The fields populated depend on the service response and how the application maps that data to its form. Developers should consult the API Reference for the response schema rather than assume that every field required by their application will be supplied.

Choose Validator when the requirement is to check postcode existence, and Autofill when the application needs associated address and location data.

Navigation Partners and Maps — Now Open

Applications are now open for ride-hailing platforms to become navigation partners.

The integration enables users to open a postcode destination in a participating ride-hailing application and continue with a ride request. This connects the location identified through the postcode system to the platform handling the journey.

If you operate a ride-hailing platform, apply to become a navigation partner to discuss integration requirements and onboarding.

Logistics Maps and Routing Engine — Coming Soon

The Logistics maps and routing engine will support routing use cases involving postcode destinations. This capability is not yet available. Supported features and integration requirements will be detailed when released.

Documentation and Next Steps

To prepare your integration, refer to:

• Service documentation: explanations, use cases and guidance on choosing a service.
• API Reference: request formats, response fields, error handling and integration requirements.