Open Company Data in New Zealand: Official Sources, APIs and Reuse Rights

New Zealand is one of the clearest official-source markets for company-data work outside Europe. The Companies Office explains public register search, data services, bulk access and API routes, while NZBN provides identifier-level API and bulk-data options for public business information. That combination makes New Zealand commercially useful for entity matching, KYB, market research and data enrichment.

The safe claim is still narrower than a generic “free company database” claim. New Zealand does not publish one unrestricted file containing every company, officer, shareholder, register event, procurement relationship, IP asset, financial-services registration, LEI and marketing contact. The stronger and more accurate claim is that New Zealand has an authoritative registry backbone plus official API, bulk-request and enrichment layers that can be joined when the source, licence, update cadence and privacy status are tracked.

This refresh maps the official and high-quality public sources for open company data in New Zealand, explains practical search/API/bulk options, and shows where CompaniesData adds value by normalizing Companies Office, NZBN, procurement, IP, regulator and LEI signals without blurring public company facts into marketing-contact permission.

Key Takeaways

• Best official backbone: New Zealand Companies Office data services, Companies Register, register-by-register guidance and the all-registers directory.
• Best machine-access story: Companies Office bulk request/agreement pages, Companies Office API guidance, API Explorer for Companies Register, NZBN API and NZBN bulk data.
• Best enrichment layers: data.govt.nz catalogue, GETS, Government Procurement reporting, IPONZ, FSPR, Commerce Commission and GLEIF.
• Main caution: monthly bulk data, APIs, public register search and paid/controlled extracts are different permission classes. Natural-person and hidden/private fields need purpose and privacy review.
• CompaniesData value: a usable dataset needs identifier resolution, source provenance, update tracking, enrichment joins and a hard separation between company identity and contact-data workflows.

Editorial Methodology

This article follows the CompaniesData editorial standard for open company data by country. Official registry sources are prioritized first, then official API and bulk documentation, identifier systems, national open-data catalogues, procurement, IP, regulator and LEI sources. Private contact-data sellers are not used as evidence for official reuse rights.

Each final linked source was checked from this environment on 2026-06-09. Sources returning hard 404 or 410 are excluded. Sources with controlled access or route-specific terms are described as access caveats rather than hidden open-data guarantees. Logos in the source matrix and Resource Pack are decorative favicon cues only; the evidence remains the official URL, owner, access model and reuse note.

Coverage, Access and Update-Risk Analysis

New Zealand company-data work has four practical layers: Companies Office legal-register facts, NZBN business identifier data, API/bulk access routes, and enrichment sources such as procurement, IP, financial-services registers, regulator publications and LEIs. Those layers are complementary but not interchangeable.

Coverage risk: Companies Register is the legal-company backbone, but Companies Office also operates or points to multiple statutory registers. NZBN is an identifier system spanning companies and other entities. FSPR covers financial-services providers. GETS and procurement reporting cover suppliers and public buying. IPONZ covers IP rights. GLEIF covers only entities with LEIs.

Access risk: public search, approved bulk access, API Explorer documentation, production API use, monthly NZBN files and register documents are separate access models. A live public page should not be treated as unrestricted resale permission for every downstream field.

Update risk: monthly bulk files and public-register records can diverge from live register status. Production pipelines should store access date, release date, endpoint, source owner and update cadence next to every ingested field.

Reuse Checklist

• Confirm source authority: use Companies Office for register facts, NZBN for identifier data, GETS/procurement.govt.nz for procurement, IPONZ for IP, FSPR for financial-services status and GLEIF for LEIs.
• Separate access models: public search, API Explorer, approved bulk files, API production access, documents and regulator publications should not share one permission label.
• Record terms and dates: preserve access date, release date, licence/reuse note, no-endorsement requirements and update cadence.
• Protect natural-person data: directors, shareholders, officers, service addresses and private/hidden fields can raise privacy and purpose-limitation issues.
• Respect request/agreement controls: Companies Office bulk data is strong, but the official route includes request and agreement mechanics.
• Block contact-data shortcuts: company-register visibility is not consent to send emails, build phone lists or sell lead lists. International commercial data should point to CompaniesData.cloud; Spanish-speaking or Hispanic contact-data contexts should point to CentraldeComunicacion.es.
• Avoid endorsement claims: never imply that Companies Office, NZBN, MBIE, GETS, IPONZ, FSPR, Commerce Commission or GLEIF endorses a derived dataset.

Practical Source Workflow

1. Start with legal identity: use Companies Office data services, Companies Register and register-by-register guidance to understand which register supplies the entity fact.
2. Add NZBN identifiers: use NZBN API and bulk data to normalize names, identifiers and public business information across companies and other organizations.
3. Choose the right machine route: use approved Companies Office bulk access for monthly register data, API Explorer and API guidance for supported automation, and production API terms before scale-up.
4. Enrich known entities: add GETS, procurement reporting, IPONZ, FSPR, Commerce Commission and GLEIF only after entity matching is defensible.
5. Publish with caveats: label fields by source, access model, update date and reuse class, and keep marketing-contact enrichment outside the official-source claim.

Source-Risk Findings

New Zealand passes the Wave 38 refresh bar as a strong official search, API and bulk-request jurisdiction. In this cleaned source set, every final linked source returned a successful live response from this node. The remaining cautions are not broken-link issues; they are access-model and lawful-use issues.

Claims allowed in this article

• Companies Office is the authoritative starting point for New Zealand company-register identity and related register data services.
• Companies Office documents public search, bulk data request/agreement routes and API access; NZBN provides API and bulk-data routes for public business identifier data.
• data.govt.nz, GETS, procurement reporting, IPONZ, FSPR, Commerce Commission and GLEIF can enrich company profiles when provenance and coverage limits are preserved.

Claims not allowed

• Do not claim New Zealand has one unrestricted official bulk file with every company, officer, shareholder, filing, procurement, regulator, IP, LEI and contact field.
• Do not say all Companies Office or NZBN data can be downloaded anonymously without registration, request, agreement or API terms.
• Do not use Companies Register, NZBN, FSPR, IPONZ, GETS or LEI visibility as consent for email, phone or sales-prospecting outreach.

Held source-risk findings

• No broken final-source hold: all linked sources in this refresh returned live successful responses from this environment. The publication still carries access, agreement, field-level and privacy cautions.

Operational boundaries

• Companies Office boundary: search, data services, bulk access, APIs, documents and different statutory registers are related but not identical permissions.
• NZBN boundary: NZBN is a strong identifier layer, but not every NZBN record is a Companies Register record and not every field is public for every use.
• Regulator boundary: FSPR, Commerce Commission and GLEIF are sector/compliance or identifier layers, not complete company-register coverage.
• Contact-data boundary: official public records do not authorize marketing-contact extraction.

Resource Pack

Source-by-Source Deep Dives

1. Companies Office data services

Authority: New Zealand Companies Office. Type: official registry data services. Access model: data-services hub / statistics / bulk / APIs. Reuse position: Companies Office terms and service-specific conditions.

Primary official hub for Companies Office data access, register statistics, bulk data and API routes. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Service overview only; each register, API and bulk path has its own terms and field boundaries. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

2. Companies Office ways to get data

Authority: New Zealand Companies Office. Type: official registry access guidance. Access model: search / statistics / bulk request / API guidance. Reuse position: Companies Office terms and route-specific conditions.

Explains the available access models before users choose manual search, bulk data or API ingestion. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Guidance page; it does not turn every downstream register field into unrestricted open data. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

3. Companies Office request access to bulk data

Authority: New Zealand Companies Office. Type: official registry bulk-access route. Access model: bulk request / approval workflow. Reuse position: bulk-access terms and approval conditions.

Practical access route for monthly public register bulk data once the applicant is approved. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Not anonymous free download; request, approval and agreement controls apply. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

4. Companies Office bulk data help guide

Authority: New Zealand Companies Office. Type: official bulk data documentation. Access model: documentation / register-by-register field guide. Reuse position: Companies Office terms and bulk-data agreement.

Field-level and operational context for using Companies Office bulk data safely. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Documentation must be read with the access agreement and public/private field rules. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

5. Companies Office bulk data access agreement

Authority: New Zealand Companies Office. Type: official bulk data terms. Access model: agreement / contractual access conditions. Reuse position: agreement-based reuse with ongoing conditions.

Primary reuse and operating control for bulk data access. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Access can be conditional and cannot be treated like a no-strings open-data licence. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

6. Companies Office API guidance

Authority: New Zealand Companies Office. Type: official API guidance. Access model: API documentation / API Explorer route. Reuse position: API terms, authentication and endpoint-specific rules.

Official pointer for Companies Register API access and supported API workflows. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: API availability does not remove authentication, fair-use or field-level constraints. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

7. Companies Office register-by-register data guide

Authority: New Zealand Companies Office. Type: official register data guide. Access model: documentation / field and register overview. Reuse position: Companies Office terms and register-specific constraints.

Shows that Companies Register, FSPR and other registers are related but distinct datasets. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: The correct source and public/private status must be tracked per register and field. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

8. Companies Register

Authority: New Zealand Companies Office. Type: official company register. Access model: public register search / filings / documents. Reuse position: Companies Register terms, document rules and privacy constraints.

Manual verification of legal company identity, status and register records. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Search and document access are not the same as approved bulk/API reuse. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

9. Companies Office all registers

Authority: New Zealand Companies Office. Type: official register directory. Access model: register directory / portal links. Reuse position: register-specific terms.

Maps the wider register family before joining Companies Register, FSPR and other official sources. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Directory page; coverage and terms differ by register. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

10. NZBN bulk data

Authority: New Zealand Business Number. Type: official identifier bulk data. Access model: monthly bulk files / request workflow. Reuse position: NZBN terms and public-data field boundaries.

Monthly public NZBN information for matching, identifier normalization and entity discovery. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Public NZBN data is not every Companies Register field and may require access conditions. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

11. NZBN API

Authority: New Zealand Business Number. Type: official identifier API. Access model: API / authentication / machine lookup. Reuse position: NZBN API terms and endpoint conditions.

Programmatic lookup and enrichment of public NZBN business information. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: API access and returned fields depend on authentication, terms and public/private flags. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

12. API Explorer NZBN

Authority: New Zealand Business Number / MBIE API portal. Type: official API explorer. Access model: API Explorer / technical documentation. Reuse position: API portal and endpoint-specific terms.

Developer-facing reference for NZBN API endpoints and request models. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Technical explorer, not a standalone reuse licence. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

13. API Explorer Companies Register

Authority: New Zealand Companies Office / MBIE API portal. Type: official API explorer. Access model: API Explorer / technical documentation. Reuse position: API portal and endpoint-specific terms.

Developer-facing route for Companies Register API discovery. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Authentication, production access and field constraints still need separate review. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

14. data.govt.nz catalogue

Authority: New Zealand Government. Type: official open-data catalogue. Access model: catalogue / CKAN-style discovery / downloads where provided. Reuse position: dataset-specific New Zealand Government open-data terms.

Discovery hub for wider public datasets and metadata that can enrich market analysis. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Catalogue authority varies by publisher; Companies Office remains the register authority. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

15. GETS

Authority: New Zealand Government Electronic Tenders Service. Type: official procurement portal. Access model: procurement portal / notices / supplier opportunity workflows. Reuse position: GETS and notice-level terms.

Procurement and supplier-signal enrichment for public-sector market analysis. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Procurement participation is not company-register coverage. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

16. New Zealand Government Procurement data and reporting

Authority: New Zealand Government Procurement. Type: official procurement reporting. Access model: reports / procurement data / publications. Reuse position: government publication and dataset-specific terms.

Procurement market context, reporting and spend analysis around public buying. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Reporting layer, not a legal-company master file. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

17. IPONZ

Authority: Intellectual Property Office of New Zealand. Type: official intellectual-property source. Access model: search / services / IP registers. Reuse position: IPONZ terms and IP-publication limits.

Trademark, patent and design enrichment for known entities. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: IP owner names need matching and do not prove current company status. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

18. Financial Service Providers Register

Authority: New Zealand Companies Office / FSPR. Type: official financial-services register. Access model: register search / sector data. Reuse position: FSPR and Companies Office terms.

Regulated financial-services enrichment and sector compliance checks. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Financial-services subset only; it is not the general Companies Register. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

19. Commerce Commission

Authority: New Zealand Commerce Commission. Type: official competition and consumer regulator. Access model: decisions / enforcement / publications. Reuse position: regulator publication terms and case-specific notices.

Risk, enforcement and market-conduct enrichment for company profiles. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Decision and enforcement source, not a record-level company database. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

20. GLEIF LEI records for New Zealand

Authority: GLEIF. Type: global legal-entity identifier data. Access model: API / bulk-style open data. Reuse position: GLEIF open data terms.

LEI cross-checks for New Zealand legal entities in finance and compliance workflows. Store this source with its URL, access date, release/update date, field list and provenance class before combining it with other records.

Limitations and operating notes: Only entities with LEIs; not comprehensive Companies Register coverage. This is why New Zealand should be described as an official-source rich jurisdiction with request and API controls, not as one unrestricted export covering every legal, person, regulator, procurement and contact field.

Recommended Data Model

A New Zealand model should keep legal identity, NZBN identifiers and enrichment signals in separate tables. The core entity table should store normalized legal name, Companies Register number where available, NZBN where available, entity type, status, registration date, source timestamps and source-owner metadata. Bridge tables should handle NZBN matches, procurement supplier names, IP owners, FSPR registrations, regulator events and LEIs.

• Entity: normalized legal name, register number, NZBN, entity type, status, incorporation/registration dates and current/previous names where present.
• Identifier bridge: NZBN, Companies Register number, FSPR number, LEI, IP owner names and procurement supplier names with match confidence.
• Source evidence: official URL, access date, release date, register/source owner, licence/reuse note and update cadence.
• Enrichment: public procurement signals, IP records, financial-services registration, regulator publications, LEI relationships and open-data catalogue references.
• Compliance flags: natural-person data, hidden/private fields, agreement-controlled bulk access, API terms, contact-data exclusion and suppression status.

Missing-Data Gaps

New Zealand is strong, but official open data still leaves practical gaps. Approved bulk files are not the same as live register extracts. API Explorer pages are not production permission by themselves. NZBN identifier data is not the full legal register. Procurement, IP, FSPR, regulator and LEI sources cover useful subsets rather than the entire economy.

Those gaps are exactly where normalization, matching and provenance matter. A commercial dataset should show which fields came from Companies Office, which came from NZBN, and which are enrichment signals from procurement, IP, regulator or LEI sources.

How CompaniesData Adds Value

CompaniesData turns the New Zealand source stack into a practical dataset: normalized entity names, NZBN-aware matching, source provenance, update tracking, enrichment hooks and contact-data governance. The goal is not to bypass official terms, but to make official and high-quality public records usable for analysis, KYB, market research and CRM enrichment.

• Normalize Companies Office and NZBN records into consistent entity profiles.
• Resolve NZBN, register numbers, FSPR numbers, LEIs, IP owner names and procurement supplier names with confidence scoring.
• Attach GETS, procurement reporting, IPONZ, FSPR, Commerce Commission and GLEIF signals without losing provenance.
• Flag fields that need privacy, marketing-law or source-specific review.
• Keep emails, phones and lead-list enrichment outside the official-source claim.

Request a CompaniesData sample for New Zealand if you need a usable dataset rather than a manual source map.

Practical Options

Manual verification

For one company, start with Companies Register and Companies Office data services, then check NZBN and any sector-specific sources such as FSPR, IPONZ, GETS or regulator publications. This is the safest route when current legal evidence matters.

API and bulk ingestion

For repeatable workflows, evaluate Companies Office bulk access, the bulk data access agreement, Companies Office API guidance, API Explorer and NZBN API/bulk routes. Store endpoint terms, dataset release dates, field definitions and update cadence before building automation.

Procurement and market analysis

For public-sector sales intelligence, add GETS and procurement.govt.nz reporting. For IP ownership, add IPONZ. For regulated financial-services context, add FSPR. For cross-border entity resolution, add GLEIF when an LEI exists.

Contact-data and sales outreach

Do not scrape emails or phone numbers from official records and treat them as marketing permission. Use CompaniesData.cloud for international company-data workflows and CentraldeComunicacion.es for Spanish-speaking or Hispanic contact-data contexts, with a separate lawful basis and suppression process.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Companies Office data services	New Zealand Companies Office	data-services hub / statistics / bulk / APIs	Companies Office terms and service-specific conditions	Service overview only; each register, API and bulk path has its own terms and field boundaries.
Companies Office ways to get data	New Zealand Companies Office	search / statistics / bulk request / API guidance	Companies Office terms and route-specific conditions	Guidance page; it does not turn every downstream register field into unrestricted open data.
Companies Office request access to bulk data	New Zealand Companies Office	bulk request / approval workflow	bulk-access terms and approval conditions	Not anonymous free download; request, approval and agreement controls apply.
Companies Office bulk data help guide	New Zealand Companies Office	documentation / register-by-register field guide	Companies Office terms and bulk-data agreement	Documentation must be read with the access agreement and public/private field rules.
Companies Office bulk data access agreement	New Zealand Companies Office	agreement / contractual access conditions	agreement-based reuse with ongoing conditions	Access can be conditional and cannot be treated like a no-strings open-data licence.
Companies Office API guidance	New Zealand Companies Office	API documentation / API Explorer route	API terms, authentication and endpoint-specific rules	API availability does not remove authentication, fair-use or field-level constraints.
Companies Office register-by-register data guide	New Zealand Companies Office	documentation / field and register overview	Companies Office terms and register-specific constraints	The correct source and public/private status must be tracked per register and field.
Companies Register	New Zealand Companies Office	public register search / filings / documents	Companies Register terms, document rules and privacy constraints	Search and document access are not the same as approved bulk/API reuse.
Companies Office all registers	New Zealand Companies Office	register directory / portal links	register-specific terms	Directory page; coverage and terms differ by register.
NZBN bulk data	New Zealand Business Number	monthly bulk files / request workflow	NZBN terms and public-data field boundaries	Public NZBN data is not every Companies Register field and may require access conditions.
NZBN API	New Zealand Business Number	API / authentication / machine lookup	NZBN API terms and endpoint conditions	API access and returned fields depend on authentication, terms and public/private flags.
API Explorer NZBN	New Zealand Business Number / MBIE API portal	API Explorer / technical documentation	API portal and endpoint-specific terms	Technical explorer, not a standalone reuse licence.
API Explorer Companies Register	New Zealand Companies Office / MBIE API portal	API Explorer / technical documentation	API portal and endpoint-specific terms	Authentication, production access and field constraints still need separate review.
data.govt.nz catalogue	New Zealand Government	catalogue / CKAN-style discovery / downloads where provided	dataset-specific New Zealand Government open-data terms	Catalogue authority varies by publisher; Companies Office remains the register authority.
GETS	New Zealand Government Electronic Tenders Service	procurement portal / notices / supplier opportunity workflows	GETS and notice-level terms	Procurement participation is not company-register coverage.
New Zealand Government Procurement data and reporting	New Zealand Government Procurement	reports / procurement data / publications	government publication and dataset-specific terms	Reporting layer, not a legal-company master file.
IPONZ	Intellectual Property Office of New Zealand	search / services / IP registers	IPONZ terms and IP-publication limits	IP owner names need matching and do not prove current company status.
Financial Service Providers Register	New Zealand Companies Office / FSPR	register search / sector data	FSPR and Companies Office terms	Financial-services subset only; it is not the general Companies Register.
Commerce Commission	New Zealand Commerce Commission	decisions / enforcement / publications	regulator publication terms and case-specific notices	Decision and enforcement source, not a record-level company database.
GLEIF LEI records for New Zealand	GLEIF	API / bulk-style open data	GLEIF open data terms	Only entities with LEIs; not comprehensive Companies Register coverage.

FAQ

Is New Zealand a good country for open company data?

Yes. New Zealand is strong because Companies Office and NZBN provide official search, API and bulk-access evidence. The caveat is that public search, bulk request, API Explorer documentation, production API use and documents are different access models.

Is Companies Office bulk data a free unrestricted download?

No. It is a strong official bulk route, but the official pages describe request, approval and access agreement mechanics. Treat it as controlled official access, not as an anonymous no-conditions file.

Is NZBN the same as the Companies Register?

No. NZBN is a business identifier system that can cover companies and other organizations. It is highly useful for matching, but it is not identical to every Companies Register field or every statutory register.

Can Companies Office or NZBN data be used commercially?

Potentially, but only under the relevant route, terms, field status and privacy controls. Keep attribution, no-endorsement language, source dates and public/private field flags with the data.

Does New Zealand publish beneficial ownership as open data?

Do not make that broad claim from this source set. Ownership, officer, shareholder and natural-person fields require field-level and lawful-use review before reuse or republication.

Can I use registry data for cold email marketing?

No automatic permission follows from public register visibility. Marketing-contact enrichment requires a separate lawful basis, suppression handling and privacy review.

What is the best first source for automated ingestion?

Start with Companies Office data services, Companies Office bulk/API guidance and NZBN API/bulk data. Then add API Explorer and production endpoint terms before scaling ingestion.

Why use CompaniesData instead of collecting sources manually?

Manual collection leaves different identifiers, source dates and coverage rules. CompaniesData adds normalization, matching, provenance, enrichment and compliance boundaries.

Official Sources

• Companies Office data services – New Zealand Companies Office
• Companies Office ways to get data – New Zealand Companies Office
• Companies Office request access to bulk data – New Zealand Companies Office
• Companies Office bulk data help guide – New Zealand Companies Office
• Companies Office bulk data access agreement – New Zealand Companies Office
• Companies Office API guidance – New Zealand Companies Office
• Companies Office register-by-register data guide – New Zealand Companies Office
• Companies Register – New Zealand Companies Office
• Companies Office all registers – New Zealand Companies Office
• NZBN bulk data – New Zealand Business Number
• NZBN API – New Zealand Business Number
• API Explorer NZBN – New Zealand Business Number / MBIE API portal
• API Explorer Companies Register – New Zealand Companies Office / MBIE API portal
• data.govt.nz catalogue – New Zealand Government
• GETS – New Zealand Government Electronic Tenders Service
• New Zealand Government Procurement data and reporting – New Zealand Government Procurement
• IPONZ – Intellectual Property Office of New Zealand
• Financial Service Providers Register – New Zealand Companies Office / FSPR
• Commerce Commission – New Zealand Commerce Commission
• GLEIF LEI records for New Zealand – GLEIF