# Visa Sponsor Check: UK, US H-1B, Canada, Netherlands (`jp-data-lab/global-visa-sponsors`) Actor

Check if an employer sponsors work visas, or list sponsors, from official data: UK licensed sponsors, US H-1B LCA filings with wages, Canada LMIA employers and Dutch recognised sponsors. Track new and removed sponsors. No personal names.

- **URL**: https://apify.com/jp-data-lab/global-visa-sponsors.md
- **Developed by:** [JP Data Lab](https://apify.com/jp-data-lab) (community)
- **Categories:** Jobs
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 employers

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Visa Sponsor Check: UK, US H-1B, Canada, Netherlands

Check whether an employer sponsors work visas, or list sponsors by place, route or occupation, from four official government sources in one format:

| Country | Official source | Employers listed | Updated |
|---|---|---|---|
| United Kingdom | [Register of licensed sponsors: workers](https://www.gov.uk/government/publications/register-of-licensed-sponsors-workers) (UK Visas and Immigration) | About 113,000 | Most working days |
| United States | [LCA disclosure data](https://www.dol.gov/agencies/eta/foreign-labor/performance) for H-1B, H-1B1 and E-3 (Department of Labor) | About 53,000 | Quarterly |
| Canada | [Positive LMIA Employers List](https://open.canada.ca/data/en/dataset/90fed587-1364-4f33-a9ee-208181dc0b97) (Employment and Social Development Canada) | About 23,000 | Quarterly |
| Netherlands | [Public Register Recognised Sponsors: Work](https://ind.nl/en/public-register-recognised-sponsors/public-register-work) (IND) | About 12,000 | Monthly |

Use it to screen job leads before applying, add a "sponsors visas" flag to a job board, find employers for immigration or recruitment outreach, watch for new and removed UK sponsors, or give an AI agent a way to answer "does this company sponsor visas?". The US data adds what the registers do not have: filing counts, top occupations and median offered wages per employer.

This is a list of organisations, not people. It has no contact names, attorneys, street addresses, phones or emails.

### Three ways to use it

**Check employers.** Put names in `employers`. Every selected country is searched, and the other filters are ignored:

```json
{ "employers": ["Deloitte", "Barclays Bank", "Shopify"] }
```

Each country gets the exact match if there is one (ignoring case, accents and forms like Ltd or Inc). Otherwise you get up to five employers whose names contain all your words, marked `"matchType": "partial"`. Names with no match are listed under `employersNotFound` in `RUN_SUMMARY` and are not charged.

**List sponsors.** Leave `employers` empty and filter:

```json
{ "countries": ["US"], "occupations": ["software"], "locations": ["TX"], "maxItems": 200 }
```

```json
{ "countries": ["GB"], "visaRoutes": ["Skilled Worker"], "locations": ["Manchester"], "keywords": ["care"] }
```

Canada and the US are sorted by approved positions, largest first. The UK and the Netherlands have no such figure, so they are sorted by name.

**Track changes.** Schedule a run with `onlyChanges` on, and each run returns what changed since the last one with the same filters:

```json
{ "countries": ["GB"], "onlyChanges": true, "maxItems": 1000 }
```

The first run saves a baseline to a key-value store in your account and returns nothing. Later runs mark each row `added`, `removed` or `changed`. A `changed` row means the visa routes or the UK rating changed, for example from A to B. If a source fails or shrinks by half or more, that country is skipped and the baseline is kept, so a bad download cannot look like mass removals.

### Output

One item per employer. Fields a source does not have are `null` or empty.

```json
{
  "country": "US",
  "countryName": "United States",
  "employerName": "Google LLC",
  "nameConfirmed": true,
  "registrationNumber": null,
  "city": "Mountain View",
  "region": "CA",
  "visaRoutes": ["H-1B", "E-3 Australian", "H-1B1 Singapore", "H-1B1 Chile"],
  "sponsorRatings": [],
  "approvedCases": 7423,
  "deniedCases": 11,
  "withdrawnCases": 52,
  "approvedPositions": 8710,
  "medianAnnualWageUsd": 193000,
  "occupations": [
    { "title": "Software Developers", "cases": 4954, "medianAnnualWageUsd": 193000 },
    { "title": "Information Technology Project Managers", "cases": 346, "medianAnnualWageUsd": 200000 }
  ],
  "naicsCode": "541512",
  "lastDecisionDate": "2026-06-30",
  "coveragePeriod": "FY2026 Q1-Q3 (October 2025 to June 2026)",
  "dataAsOf": "2026-06-30",
  "matchedQuery": "Google",
  "matchType": "exact",
  "change": null,
  "sourceName": "LCA Programs disclosure data (U.S. Department of Labor, OFLC)",
  "sourceUrl": "https://www.dol.gov/agencies/eta/foreign-labor/performance",
  "attribution": "Source: U.S. Department of Labor. Aggregated by employer. Not endorsed by or affiliated with the Department of Labor.",
  "scrapedAt": "2026-11-01T09:00:00+00:00"
}
```

This example is a real row, with the `occupations` list cut to two of its five entries.

| Field | Meaning |
|---|---|
| `country` | `GB`, `US`, `CA` or `NL` |
| `employerName` | Name on the official record, or `null` if it could not be confirmed as an organisation |
| `nameConfirmed` | `false` when the name and place are hidden. See below |
| `registrationNumber` | Dutch KVK number. Other sources have none |
| `city`, `region` | City, plus county (UK), state (US) or province (Canada). The Dutch register has no location |
| `visaRoutes` | UK routes, US visa classes, Canadian LMIA streams |
| `sponsorRatings` | UK only, for example `Worker (A rating)`. A B rating means UKVI found compliance problems |
| `approvedCases` | US: certified LCAs. Canada: positive LMIAs |
| `deniedCases`, `withdrawnCases` | US only |
| `approvedPositions` | Positions on those approvals |
| `medianAnnualWageUsd` | US only. Median offered wage on certified LCAs, converted to a yearly figure |
| `occupations` | US and Canada: the top five occupations, with wages in the US |
| `naicsCode` | US only: the employer's industry code |
| `coveragePeriod` | The period the row covers |
| `dataAsOf` | The date of the source data, so you can see how fresh it is |
| `matchedQuery`, `matchType` | The name you asked about and `exact` or `partial`, when checking employers |
| `change` | `added`, `removed` or `changed`, when tracking changes |

`RUN_SUMMARY` in the key-value store shows the rows read and data date per country, any source errors, and names not found.

### What these lists do and do not mean

- **Being listed does not mean an employer is hiring or will sponsor you.** It means they hold a licence, are recognised, or received an approval.
- **A US LCA is not a visa.** It is the wage filing that comes before an H-1B petition. Employers file many LCAs that never become hires, and one LCA can cover many positions, so `approvedPositions` can far exceed real headcount. Staffing firms show this most.
- **A Canadian LMIA is not a work permit.** Not every approved position leads to a worker arriving.
- **No match does not prove an employer never sponsors.** Names on the registers can differ from trading names, a company may be listed under a parent or subsidiary, and records for employers whose names could not be confirmed are left out of the US data.
- **The sources differ in meaning.** The UK and Dutch data show current status. The US and Canadian data show past approvals.

Always confirm on the official source before making a decision. This Actor gives information, not immigration advice.

### Personal data

Sole traders and small practices can appear on these lists under a person's name, so a name is shown only if it can be confirmed as an organisation: a legal form (Ltd, LLC, B.V.), or a word for an organisation (university, council, hospital). Names that start with a personal title, professional corporations of doctors and dentists, and Canadian employers marked as sole proprietorships are not shown.

Those rows never appear in lists or change tracking. If you check that exact name in the UK, Dutch or Canadian data, you get a row confirming the listing with `employerName`, city, region and number set to `null`. Unconfirmed US employers are not included at all. For `Person T/A Business`, only the trading name is shown, and only if it can be confirmed. Some real companies are left out as a result, for example those with no legal form in their name: about 89% of UK names, 94% of Dutch names and 86% of Canadian names pass, and about 95% of US filings.

### Data sources and licences

The Actor reads the official files and the published register pages only. It never logs in and never uses a job site.

- **United Kingdom:** Contains public sector information licensed under the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). Source: UK Visas and Immigration.
- **Netherlands:** Source: Immigration and Naturalisation Service (IND). The [IND proclaimer](https://ind.nl/en/proclaimer) allows reuse with the source mentioned.
- **Canada:** Contains information licensed under the [Open Government Licence – Canada](https://open.canada.ca/en/open-government-licence-canada). Source: Employment and Social Development Canada. Rows are added up per employer across quarters.
- **United States:** U.S. government work in the [public domain](https://www.dol.gov/general/aboutdol/copyright). Source: U.S. Department of Labor. The quarterly file is too large to read during a run, so it is aggregated per employer in advance and included with the Actor. `coveragePeriod` shows which release you have.

Each row carries its `attribution`, so keep it if you republish the data. This Actor is independent and is not affiliated with or endorsed by any of these governments or agencies.

### Tips

- Run `onlyChanges` daily for the UK. Canada and the US change only a few times a year.
- If `changesNotReturned` in `RUN_SUMMARY` is above 0, raise `maxItems`. The baseline still moves forward, so those rows will not come back.
- `locations` and `occupations` narrow by country: the Dutch register has no place, and the UK and Dutch registers have no occupations, so those countries return nothing with these filters.
- Use one `employers` list for all your names rather than many runs. It is cheaper and faster.

# Actor input Schema

## `employers` (type: `array`):

Optional, up to 1,000 names, e.g. Deloitte, Barclays Bank, Booking.com. Returns every matching sponsor in the selected countries, and the other filters are ignored. Matching ignores case, accents and forms like Ltd or Inc. Names with no match are listed in RUN_SUMMARY and are not charged. No match does not prove an employer never sponsors: see the README.

## `countries` (type: `array`):

Leave empty for all four.

## `keywords` (type: `array`):

Keep employers whose name contains any of these words, e.g. bank, software.

## `locations` (type: `array`):

Keep employers in any of these places: a city (London, Toronto) or a US state or Canadian province code (CA, ON). The Dutch register has no location, so Dutch employers are left out when this is set.

## `visaRoutes` (type: `array`):

Keep employers on any of these routes, by part of the name: Skilled Worker, Global Business Mobility, Creative Worker (UK), H-1B, E-3 (US), Global Talent Stream, High Wage, Primary Agriculture (Canada).

## `occupations` (type: `array`):

US and Canada only. Keep employers with these words in their top occupations, e.g. software, nurse. UK and Dutch employers are left out when this is set, because those registers have no occupations.

## `minApprovedPositions` (type: `integer`):

US and Canada only. UK and Dutch employers are left out when this is above 0. In the US this counts positions on certified LCAs, not people hired.

## `onlyChanges` (type: `boolean`):

For scheduled runs. Returns employers added, removed or changed since the previous run with the same filters. The first run only saves a baseline and returns nothing. The UK register changes most working days, the Dutch one monthly and Canada and the US quarterly. Ignored when checking employers.

## `canadaQuarters` (type: `integer`):

How many recent quarters of the LMIA list to add up per employer.

## `maxItems` (type: `integer`):

Total for the run, taken evenly across countries. You are charged per result. Not used when checking employers. With only changes on, raise this if RUN_SUMMARY shows changesNotReturned.

## Actor input object example

```json
{
  "employers": [],
  "countries": [],
  "keywords": [],
  "locations": [],
  "visaRoutes": [],
  "occupations": [],
  "minApprovedPositions": 0,
  "onlyChanges": false,
  "canadaQuarters": 4,
  "maxItems": 100
}
```

# Actor output Schema

## `sponsors` (type: `string`):

One item per employer: country, confirmed name, city, region, visa routes, UK rating, Dutch KVK number, approved cases and positions, US wages, top occupations, change type, data date, source and attribution.

## `runSummary` (type: `string`):

Rows read per country, data dates, any source errors, employers that were not found and change counts.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jp-data-lab/global-visa-sponsors").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("jp-data-lab/global-visa-sponsors").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call jp-data-lab/global-visa-sponsors --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jp-data-lab/global-visa-sponsors"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/jg3fBZe5iKPULccis/builds/ZhUD8LRAZ5OA0yVG1/openapi.json
