Frequently asked questions

Is StreetKit NZ Post certified?

No. StreetKit v1 should be treated as address autocomplete based on official/open address data. It does not provide NZ Post certification or delivery-point guarantees.

Does StreetKit prove an address is deliverable?

No. A physical address record can be useful for autocomplete without proving mail or courier deliverability.

What data is the first version based on?

The first version is based on official/open New Zealand address data from LINZ NZ Addresses layer 123113, prepared for StreetKit address search.

Does the widget call LINZ while a user types?

No. LINZ is a source dataset for StreetKit, but user searches are handled by StreetKit address data, not live LINZ requests.

What does StreetKit receive from my form?

The autocomplete flow only needs the typed address query and the selected address. It does not need unrelated form fields such as names, emails, carts, or accounts.

Does StreetKit support DPID, PO Box, Private Bag, or RD/mailtown addresses?

No. StreetKit v1 does not provide DPID, PO Box, Private Bag, Counter Delivery, delivered-only filtering, RD/mailtown postal addressing, postal validation, courier deliverability, or delivery guarantees.

Can I use a custom address data URL?

The widget supports a custom indexBaseUrl, which lets approved integrations point at a different StreetKit address data endpoint.

Can I use StreetKit with React or server-rendered pages?

Yes. The widget attaches to a normal input element, so it can be initialized after your framework renders that input.

Why do local searches return few results?

The local site uses a small fixture index at /index/v1. It is for demo and development use, not complete coverage.