# LinkedIn Jobs Scraper: No Login, H1B Visa Sponsorship Flags (`locaihost/linkedin-jobs`) Actor

LinkedIn jobs scraper with no login: each job flagged with the employer's real US H1B (H-1B) filing record and UK sponsor licence, the closest filed title and its median wage. Salary, seniority, applicants. New-only mode. $1.50 per 1,000 jobs; the most used LinkedIn jobs scraper charges $2.

- **URL**: https://apify.com/locaihost/linkedin-jobs.md
- **Developed by:** [locaihost data](https://apify.com/locaihost) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.85 / 1,000 job results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## LinkedIn Jobs Scraper: No Login, H1B Visa Sponsorship Flags

Search LinkedIn jobs **without logging in**, and see for every job whether the employer actually
sponsors work visas: its real **US H1B (H-1B) filing record** and its **UK sponsor licence**, matched to the
job's title.

No other LinkedIn jobs scraper tells you this. Job ads rarely say "we sponsor", and many employers that
sponsor never mention it. The filings say it for them.

```
Job                           Company   Sponsorship  Evidence
Senior Data Analyst - Growth  Wise      strong       Wise US Inc.: 11 certified H-1B/E-3 LCAs in FY2026;
                                                     A-rated UK Skilled Worker sponsor
Data Analyst                  (agency)  none         No H-1B/PERM filings (FY2024–FY2026) or UK sponsor
                                                     licence found under this name
```

### What you get per job

**From LinkedIn:** job title, company, company page, location, posted date, job link, and with full
details on: the **published salary range** (min, max, currency, period), seniority level, employment
type, industries, applicant count and the job description. Every row has the same columns: a value
LinkedIn didn't show is `null`, and `detailsFetched` is `false` on the rare job whose page LinkedIn
refused after five tries.

**Sponsorship evidence:**

- `sponsorSignal`: `strong` / `some` / `none`, from confirmed filings only
- `h1bCertifiedLatestFY`, `h1bCertifiedTotal`: certified H-1B (and H-1B1/E-3) Labor Condition
  Applications from the US Department of Labor, FY2024 to date
- `similarFiledTitle` and `similarTitleMedianWage`: the employer's filed job title closest to this
  job, and the median wage it filed for it, a useful salary benchmark (annual, in USD:
  `similarTitleWageCurrency` and `similarTitleWagePeriod` say so on every row that has a wage)
- `ukLicensed`, `ukRating`, `ukRoutes`: from the UK Home Office register of licensed sponsors
- `sponsorNote`: a plain-English sentence you can show a candidate

**Wording matters, so here's ours:** when no filings are found we say *"no filings found under this
name"*, never "doesn't sponsor". A company can sponsor under a different legal name, and big brands
are mapped to their legal entities (Meta → Meta Platforms, Inc.; PwC → PricewaterhouseCoopers…). The
flag is evidence, not legal advice.

### Who it's for

- **Job boards for international candidates:** tag every listing with real sponsorship evidence.
- **Recruiters and immigration law firms:** find employers actively filing for the roles you place.
- **Job seekers on a visa:** only spend applications on employers that sponsor this kind of role. Set
  `sponsorship` to `only-with-evidence`.

### Job alerts

Turn on **onlyNew** in a saved task and schedule it daily: each run returns only jobs that weren't in
an earlier run, so you get a clean daily alert and never pay twice for the same job.

### What it costs

**$1.50 per 1,000 jobs**, details and sponsorship flags included ($1.10 on Scale, $0.85 on Business).
Free-plan users get up to 1,000 jobs per run.

You pay only for jobs in your dataset. A job found by two of your searches is returned and charged
once. Jobs dropped by the `sponsorship` or `seniority` filters, and searches LinkedIn answers with
unrelated jobs, are not charged. If a run nears its timeout, it stops, keeps what it found and tells
you in the status message; it never ends half-saved.

### Honest limits

- **Logged-out only.** We read LinkedIn's public guest job pages, exactly what any visitor sees without
  an account. We never log in and never ask for your cookies.
- **About 1,000 results per search** is LinkedIn's own cap. Split broad searches by location.
- **Write locations in English** ("Tokyo, Japan", not "東京"). LinkedIn's public search may not
  recognise a place written in another script and then shows jobs from elsewhere; the run warns you.
- **Remote and experience filters** aren't honoured by LinkedIn's public pages, so experience is filtered
  afterwards from each job's seniority level (`seniority` input, needs full details on). That reads
  every job page, so it is slower, and many employers leave the level as "Not Applicable": a narrow
  level like "Entry level" can keep only a few jobs in a hundred. Jobs it drops are not charged.
- **Salary** appears only when the employer published one.
- **Staffing agencies** are flagged with the agency's own filings, not those of the client they're
  hiring for.
- **US filing data** is the Department of Labor's public disclosure files (public domain), refreshed
  quarterly; the latest fiscal year is partial.

### Privacy

Recruiter and hiring-team cards are removed before anything is read, and email addresses and phone numbers
typed into job descriptions are scrubbed, as is the poster's name when LinkedIn shows a poster card. A
person mentioned in an ad's free text with no poster card is not detected, so don't rely on descriptions
being name-free. Output fields are about jobs and employers, not people.

### Example

```json
{
  "keywords": ["software engineer"],
  "locations": ["United States"],
  "postedWithin": "week",
  "maxJobsPerSearch": 50,
  "sponsorship": "only-with-evidence"
}
```

### Support

Open an issue on the Actor's page. Issues are usually answered within a day.

# Actor input Schema

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

What you'd type into LinkedIn's job search, e.g. "software engineer", "data analyst". Each keyword is searched in every location.

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

Countries, cities or regions as you'd type them on LinkedIn, e.g. "United States", "London", "Berlin, Germany". Leave empty to search worldwide.

## `postedWithin` (type: `string`):

Only jobs posted in this window.

## `maxJobsPerSearch` (type: `integer`):

Per keyword and location. Leave empty for 25. LinkedIn shows at most about 1,000 results for one search.

## `includeDetails` (type: `boolean`):

Open each job for its description, published salary range, seniority level, employment type, industries and applicant count. Turn off for faster, card-only results.

## `sponsorship` (type: `string`):

"Flag" adds each employer's US H-1B filing record and UK sponsor licence to every job. "Only with evidence" keeps only jobs whose employer has filed for this kind of role or holds a UK licence. "Off" skips the check.

## `seniority` (type: `array`):

Optional. Keep only these LinkedIn seniority levels, e.g. "Entry level", "Mid-Senior level", "Associate", "Internship". Needs full job details.

## `onlyNew` (type: `boolean`):

Remembers what this saved task already returned, so a daily schedule becomes a job alert. Off by default so the first run returns everything.

## Actor input object example

```json
{
  "keywords": [
    "software engineer",
    "data scientist"
  ],
  "locations": [
    "United States",
    "London"
  ],
  "postedWithin": "week",
  "maxJobsPerSearch": 10,
  "includeDetails": true,
  "sponsorship": "flag",
  "seniority": [
    "Entry level",
    "Associate"
  ],
  "onlyNew": false
}
```

# Actor output Schema

## `jobs` (type: `string`):

One record per job posting with salary, seniority and sponsorship evidence.

## `summary` (type: `string`):

Jobs returned and skipped, block rate, field-drift check, data dates and measured cost per 1,000.

# 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 = {
    "keywords": [
        "software engineer"
    ],
    "locations": [
        "United States"
    ],
    "maxJobsPerSearch": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("locaihost/linkedin-jobs").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 = {
    "keywords": ["software engineer"],
    "locations": ["United States"],
    "maxJobsPerSearch": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("locaihost/linkedin-jobs").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 '{
  "keywords": [
    "software engineer"
  ],
  "locations": [
    "United States"
  ],
  "maxJobsPerSearch": 10
}' |
apify call locaihost/linkedin-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,locaihost/linkedin-jobs"
        }
    }
}
```

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/ADoXoJZ1TtnHvcNOj/builds/VlQJHr2VfHztpzRNo/openapi.json