🔎 New Zealand Gazette Insolvency Notice Watch

New Zealand Gazette insolvency notices as they are gazetted, across the six source-defined notice types: applications to wind up, liquidator appointments and releases, receiver and manager appointments, administrator appointments, bankruptcies, and meetings / last dates for debts and claims. Keyed on the Gazette's own notice number.

Output is one insolvency_notice_record row per result; billing is pay-per-event, the value event being one insolvency notice delta (a $0.02 start fee per run, then $0.05 per insolvency notice delta plus one $0.10 source check per run that reads the source). Source: api.digitalnz.org, gazette.govt.nz.

📊 Sample Output

Real rows from run GTPpsikmwhLVgWxfZ on build 0.1.14 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

notice_number	title	gazetted_date	notice_type	act	notice_url
2026-aw4926	Advertisement of Application for Putting Company into Liquidation	2026-08-31	Applications for Winding up/Liquidations	Companies Act	https://gazette.govt.nz/notice/id/2026-aw4926
2026-aw4922	Advertisement of Application for Putting Company into Liquidation	2026-08-31	Applications for Winding up/Liquidations	Companies Act	https://gazette.govt.nz/notice/id/2026-aw4922
2026-aw4981	Advertisement of Application for Putting Company into Liquidation	2026-08-31	Applications for Winding up/Liquidations	Companies Act	https://gazette.govt.nz/notice/id/2026-aw4981
2026-aw4915	Advertisement of Application for Putting Company into Liquidation	2026-08-31	Applications for Winding up/Liquidations	Companies Act	https://gazette.govt.nz/notice/id/2026-aw4915
2026-aw4891	Advertisement of Application for Putting Company into Liquidation	2026-08-31	Applications for Winding up/Liquidations	Companies Act	https://gazette.govt.nz/notice/id/2026-aw4891
2026-aw4890	Advertisement of Application for Putting Company into Liquidation	2026-08-31	Applications for Winding up/Liquidations	Companies Act	https://gazette.govt.nz/notice/id/2026-aw4890
2026-aw4889	Advertisement of Application for Putting Company into Liquidation	2026-08-31	Applications for Winding up/Liquidations	Companies Act	https://gazette.govt.nz/notice/id/2026-aw4889
2026-aw4888	Advertisement of Application for Putting Company into Liquidation	2026-08-31	Applications for Winding up/Liquidations	Companies Act	https://gazette.govt.nz/notice/id/2026-aw4888

The run finished with the status message: NORMAL: emitted 20 item(s)

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_key (string/null) — e.g. nzgz:2026-aw4926
• notice_number — e.g. 2026-aw4926
• title — e.g. Advertisement of Application for Putting Company into Liquidation
• gazetted_date — e.g. 2026-08-31
• notice_type — e.g. Applications for Winding up/Liquidations
• act — e.g. Companies Act
• notice_url — e.g. https://gazette.govt.nz/notice/id/2026-aw4926
• summary — e.g. This document notifies you that: On 9 July 2026, an application for putting TOK
• notice_type_code — e.g. aw
• record_type (string) — e.g. insolvency_notice_record
• delta_type (string/null) — null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "notice_types": [
    "aw",
    "al"
  ],
  "max_per_type": 10,
  "watch_mode": false,
  "baseline_id": "default"
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.05 insolvency-notice-delta = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
  "notice_types": [
    "aw",
    "al"
  ],
  "max_per_type": 10,
  "watch_mode": false,
  "baseline_id": "default"
}

A bounded run for checking the field shape before scheduling.

3. Watch mode on a schedule

{
  "notice_types": [
    "aw",
    "al"
  ],
  "max_per_type": 10,
  "watch_mode": true,
  "baseline_id": "default"
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.05 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

One real record from run GTPpsikmwhLVgWxfZ, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_key": "nzgz:2026-aw4926",
  "notice_number": "2026-aw4926",
  "title": "Advertisement of Application for Putting Company into Liquidation",
  "gazetted_date": "2026-08-31",
  "notice_type": "Applications for Winding up/Liquidations",
  "act": "Companies Act",
  "notice_url": "https://gazette.govt.nz/notice/id/2026-aw4926",
  "summary": "This document notifies you that: On 9 July 2026, an application for putting TOK 2020 LIMITED into liquidation was filed in the High Court at Tauranga. Its reference number is CIV-2026-470-156. The application is to be heard by the High Cour",
  "notice_type_code": "aw",
  "record_type": "insolvency_notice_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 0
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each insolvency notice delta is charged at the moment it is pushed (insolvency-notice-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

Source

• DigitalNZ API (Department of Internal Affairs), primary_collection = New Zealand Gazette, filtered by notice type: https://api.digitalnz.org/records.json
• Each record links to the official notice page on gazette.govt.nz (notice_url) and carries the Gazette notice number. Record metadata is published under Creative Commons Attribution 3.0 NZ (usage: share, modify, use commercially). No API key is required; a DigitalNZ key is used when the DIGITALNZ_API_KEY environment variable is set.
• Why this door (2026-09-17): gazette.govt.nz's own search path is now disallowed by its robots.txt and sits behind a bot-challenge; the Gazette names DigitalNZ as the machine-readable door for its data.

Timeliness — read this before buying

DigitalNZ ingests the Gazette's commercial notices with a delay. On 2026-09-17 the newest insolvency notices in the API were dated 2026-08-31 while the Gazette site already listed later notice numbers. Expect the watch to surface a notice roughly two to four weeks after it is gazetted. If you need same-day insolvency notices, this Actor is not the right tool; the Gazette Office issues RSS keys on request (info@gazette.govt.nz).

Snapshot mode is a PREVIEW

watch_mode: false returns at most 25 records, hard-capped in code regardless of any input, labeled output_mode: "preview". This actor sells change detection, not bulk record export.

Watch semantics

The first watch run stores a private baseline and emits zero deltas. Later runs emit NEW / CHANGED / REMOVED keyed on the source-native id with before / after and changed_fields. Billed deltas are capped at 500 per run; the overflow is reported as a named PARTIAL withholding, is never billed, and is re-detected on the next run.

Terminal states

NORMAL · SUCCEEDED-0: GENUINE_EMPTY · SUCCEEDED-0 (no change) · PARTIAL · BLOCKED. A zero with no evidence FAILS loud rather than exiting 0 quietly.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Source check (source-check)	$0.10	$0.09	$0.08	$0.07
Insolvency Notice Delta (insolvency-notice-delta)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price (watch mode, one delta per change):

• 8 insolvency notice deltas: $0.02 start + $0.10 source check + 8 × $0.05 = $0.52
• 25 insolvency notice deltas: $0.02 start + $0.10 source check + 25 × $0.05 = $1.37
• 100 insolvency notice deltas: $0.02 start + $0.10 source check + 100 × $0.05 = $5.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: emitted 20 item(s). Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by api.digitalnz.org, gazette.govt.nz. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (api.digitalnz.org, gazette.govt.nz) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other company registry checks actors?
A: Same output shape and billing model; this one covers api.digitalnz.org, gazette.govt.nz. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Fewer rows than expected → the source had fewer items in scope → widen the input.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

🔗 Related Actors

• FMCSA Motor Carrier Authority Check — Resolves USDOT numbers against the official FMCSA SAFER company snapshot — legal/DBA name, entity type, operating status, out-of-service date, MC/MX…
• 🇸🇬 MAS Financial Institutions Directory Change Watch — Auditable deltas on Singapore's MAS Financial Institutions Directory — institutions added, removed, or with a licence/profile change. Keyed on the MA…
• New York Active Corporation Check — Resolves entities against the New York Department of State active-corporations dataset — by DOS ID or exact name. One official answer per identity; a…
• Oregon New Businesses — Monthly Formation Feed — Oregon businesses registered in the latest published month, from the Secretary of State's official monthly new-business file — registry number, busin…
• Texas Franchise Taxpayer Status Check — Resolves Texas taxpayers against the Comptroller's official franchise-tax account-status service — by 11-digit taxpayer number, SOS file number or ex…
• UK Charity Eligibility Lookup — Charity Commission register — Look up UK charities on the official Charity Commission register — one verdict per query with number, name and status. No API key; pay per answer
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.