UK Gazette Insolvency Notice Watch avatar

UK Gazette Insolvency Notice Watch

Pricing

from $33.50 / 1,000 notice deltas

Go to Apify Store
UK Gazette Insolvency Notice Watch

UK Gazette Insolvency Notice Watch

Insolvency notices published in The Gazette — the UK's official public record: notice code, category, the subject named in the notice, publication timestamp…

Pricing

from $33.50 / 1,000 notice deltas

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Share

Insolvency notices published in The Gazette — the UK's official public record: notice code, category, the subject named in the notice, publication timestamp and the notice text, keyed on the Gazette's own notice id. Bounded by a publication-date window, because the archive holds over three million notices.
## Source
The Gazette insolvency notice Atom feed (public, logged-out)
- https://www.thegazette.co.uk/insolvency/notice/data.feed
Public, logged-out only — no API key, login, cookie or CAPTCHA.
## Pricing
| Event | Price (FREE tier) |
|---|---|
| Actor start (`apify-actor-start`) | $0.02 one-time |
| Source check (`source-check`) | $0.10 |

| Per delta (notice-delta) | $0.05 |

`source-check` ladder, GOLD-floored: **$0.10 / $0.09 / $0.08 / $0.067**, charged
once per run after enumeration terminates — seed and genuine-zero runs included.
The per-delta value event (`notice-delta`) is the **primary** event and is priced at **$0.05 per delta** at the FREE tier. Ladder, GOLD-floored: **$0.05 / $0.045 / $0.04 / $0.0335** (FREE / BRONZE / SILVER / GOLD-PLATINUM-DIAMOND). `source-check` still charges; it is no longer the headline event. Billed deltas are capped at 500 per run and any overflow is reported as a withholding rather than charged.
## Snapshot mode is a PREVIEW
`watch_mode: false` returns at most **25 records**, hard-capped in code regardless
of `max_items`, labeled `output_mode: "preview"`. This cell sells change detection,
not bulk record export.
## Watch semantics
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`. A build whose signature shape changes RE-SEEDS rather than
emitting a storm of deltas nobody caused.
## Source cadence
The Gazette publishes on business days and often many times a day — the 24–25 July 2026 window alone held 555 insolvency notices against an archive total of 3,313,513. The date window is what keeps a run bounded.
## Which filters are real

The Gazette accepts some filter parameters and silently ignores others. Measured against the source's own reported total (3,313,513 unfiltered):

filtereffect
publication date windowworks — 24–25 July 2026 narrowed to 555
text_queryworks — "winding up" narrowed to 1,137,436
editionworks — london narrowed to 3,020,737
notice codeignored by the source — returns 200 and changes nothing

So notice_codes is applied by this actor after fetching, and the ignored parameter is never sent. You still get the filtering; you are not told the source did it.

Subject vs submitter

subject is the party named in the notice. submitter_given_name and submitter_family_name are the Gazette submitting official — the same person appears across unrelated notices. They are never merged.

## 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.