DEV Community

Russell Yapp
Russell Yapp

Posted on

Tracking changes to the UK sponsor register with a change feed

The UK Home Office publishes a register of licensed sponsors for the Worker and Temporary Worker routes. It publishes only the latest file. If an organisation was added last month, or dropped off last week, the register does not tell you when.

I have built an Apify Actor, UK Sponsor Register Changes, that keeps that history from the day we started collecting. It has been public since 3 November 2026. This post explains what it returns, how to run it, and what it will not tell you.

Why a change feed rather than a full list

The register is useful as a lookup. It is less useful if your question is "what changed since I last looked?". Compliance, HR and immigration advisers, and analysts who follow the sector, usually want that second question answered:

  • which organisations have been added;
  • which are no longer listed;
  • which have had a rating changed;
  • which have had a route added or removed.

Comparing two large files by hand each time is slow and easy to get wrong. A feed gives you only the rows that differ, each with a date, so you pay for and read only the changes.

What a change row contains

One row per change. According to the README, each row has the date, the organisation, town, county, route, the old and new type and rating, where it came from, and its id and sequence. The README's sample row (an invented organisation, not a real one):

date changeType organisation town county route oldTypeRating newTypeRating
2026-01-05 added Example Org Ltd Exampleton Examplesire Worker null Worker (A rating)

The change types are an organisation added, no longer listed, a rating changed, or a route added or removed. "Removed" means only that the organisation is not in the file of that date. It does not say why.

How to run it

The Store page is here: https://apify.com/yappman/uk-sponsor-register-changes

The simplest input caps the run at three rows:

{"maxItems": 3}
Enter fullscreen mode Exit fullscreen mode

The Console form starts at 3 rows, so a default run costs up to $0.015. To narrow a run, the README's example input uses a start date, a change type and a county:

{"changedSince": "2026-10-19", "changeTypes": ["added"], "counties": ["West Yorkshire"], "maxItems": 50}
Enter fullscreen mode Exit fullscreen mode

Set maxItems to cap what a run can cost. A call that leaves it out returns up to 100 rows.

What it will not tell you

  • It is not advice. It is a dated record of changes to a public register. Being on the register says nothing about the status of any job or any visa outcome.
  • It is not a compliance check on a named employer. I do not offer it as a way to confirm an employer's current standing.
  • It does not have the register's full history. The register publishes only its latest file, so history starts on the day we began collecting. Collection is intended each working day, and any day we missed is listed in RUN_SUMMARY (daysMissed).
  • It does not give names of individuals, by design. Entries that look like an individual's name are designed to be left out and counted in RUN_SUMMARY (withheldByType; counts under 5 show as <5). The check is rule-based and can be wrong both ways. It can leave out a genuine organisation, and it can let through a company, school or trading name that belongs to one person.
  • It holds back unusual days. If a comparison shows more than 3% of the register changing in one day, we hold it back for checking rather than publish it.
  • Your use is your responsibility. We cannot control what happens to rows once they are delivered.

Cost

Pay per event: $0.005 for each change row returned, which is $5.00 per 1,000. The price is the same on every plan, with no start fee and no run fee. A run that is refused before any data is read, that finds no changes in your window, or that finds the change log unavailable costs nothing.

Some figures from the README: a run capped at 3 rows costs up to $0.015; a run with no cap returns up to 100 rows, so up to $0.50. For comparison with other tools, check other sponsor-register Actors on the Store yourself; I make no claim about relative price.

Privacy

The rows are organisation names from a public register, and some organisations are sole traders. The privacy notice for this feed, including how to object or ask for an entry to be removed, is at https://data.yappman.com/privacy/. A removal changes our record and later runs. It cannot recall rows already delivered.

Licence and attribution

Contains public sector information licensed under the Open Government Licence v3.0. Source: Register of licensed sponsors: workers, UK Visas and Immigration, GOV.UK.

Not affiliated with or endorsed by the Home Office or UK Visas and Immigration.

I would like to hear if a field is missing or a row looks wrong. Ratings and reviews on the Store page also help other buyers judge whether it fits.

Russell Yapp, Yappman Data

Top comments (0)