# Visa Sponsorship & H1B Jobs Scraper — US Jobs That Sponsor (`northbell/visa-sponsorship-jobs-scraper`) Actor Every US tech job whose employer says it will sponsor a work visa (H1B / H-1B and similar), from Dice: title, company, location, remote flag, employment type, posting date, full description — plus job alerts: only jobs new since your last run. Leave the search empty for all ~900. No login. - **URL**: https://apify.com/northbell/visa-sponsorship-jobs-scraper.md - **Developed by:** [Northbell](https://apify.com/northbell) (community) - **Categories:** Jobs, Lead generation - **Stats:** 4 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.60 / 1,000 jobs 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 ## Visa Sponsorship & H1B Jobs Scraper Every **US tech job whose employer says it is willing to sponsor a work visa** (H-1B and similar) — about 900 at any time, all of them in one run, as clean JSON with full descriptions. The flag comes from the employer on Dice, not from guessing at the job text. Schedule it daily and it tells you **exactly which sponsoring jobs are new and which have closed**, because the whole list fits in one run. > **Don't know which companies to watch?** The [Greenhouse Jobs Scraper](https://apify.com/northbell/greenhouse-jobs-scraper) searches **4,800 companies by job title** — no company names needed — and reports exactly which matching roles are new or closed each run. ### How "new since last run" works The Actor remembers which jobs each search returned last time. A job it has not seen before is marked `isNewSinceLastRun: true`. If the whole search fits within **Max jobs**, the comparison is exact and jobs that disappeared come back as `type: "closed"` rows. If the search is bigger than Max jobs, a job only counts as new when it was also posted after your previous run — so an old job that merely moved into view is never reported as new. Filters (title, location text, salary, remote) never change the comparison, so changing a filter never makes jobs look new. ### What you get | Field | | |---|---| | `title`, `company`, `location` | as listed | | `employmentType`, `remote`, `employerType` | Full-time / Contract…, remote flag, direct hire or recruiter | | `easyApply`, `willingToSponsor` | Dice's easy-apply and visa-sponsorship flags | | `summary`, `description` | Dice's summary and the full job text (turn off with *Include the full description*) | | `postedAt`, `updatedAt` | dates from Dice | | `companyUrl`, `companyLogo` | the company's Dice page and logo | | `isNewSinceLastRun` | `true` / `false`, or `null` on the first run (unknown, not "old") | | `jobUrl` | link to the job on Dice | | `search` | which of your searches returned it | ### Input Put one search per line in **Searches** (e.g. `software engineer`) and optionally a **Location** (e.g. `Texas`). Many searches in one run are cheaper than one run each. A search the site refuses comes back as an `error` row and the run carries on. ### Example output One real row from a test run (long text shortened here with …). ```json { "type": "job", "provider": "visasponsor", "search": "data", "jobId": "fe624061-c484-4bda-9e6f-b56069a7d41f", "title": "Google Cloud Platform Data Architect", "company": "Logisoft Technologies Inc", "location": "Atlanta, Georgia, USA", "employmentType": "Contract, Third Party", "remote": false, "salaryText": "Depends on Experience", "easyApply": true, "willingToSponsor": true, "employerType": "Direct Hire", "summary": "Hello Connections, Role: Google Cloud Platform Data Architect Location: Atlanta, GA Need Google Cloud Platform certification MUST JOB Description: Design, bui…", "postedAt": "2026-10-06T12:59:39.000Z", "updatedAt": "2026-10-06T12:59:39.000Z", "jobUrl": "https://www.dice.com/job-detail/fe624061-c484-4bda-9e6f-b56069a7d41f", "companyUrl": "https://www.dice.com/company/10506774", "companyLogo": "https://d3qscgr6xsioh.cloudfront.net/Slwfu95dQj6VynYwzO6J_bdaf1890ad91cfc4f483c70f305bd459.png?format=webp", "countryCode": "US", "seniority": "lead", "employmentTypes": [ "contract" ], "description": "Hello Connections,\nRole: Google Cloud Platform Data Architect\nLocation: Atlanta, GA \n\nNeed Google Cloud Platform certification MUST \nJOB Description: \n- Design,…", "isNewSinceLastRun": false } ``` ### Get only the new jobs every morning (3 steps) 1. Open this Actor in Apify Console, fill in your searches, set **What to return** to **Only jobs that are new since the last run**, and click **Save as a new task**. 2. On the task, add a **Schedule** — for example daily at 07:00. 3. Open the task's **Integrations** tab and connect **Slack**, **email**, **Google Sheets** (or Zapier / Make / a webhook). Each morning you get only the new jobs. You pay only for the new jobs plus $0.01 per run, so a quiet day costs about a cent. When you export by hand, pick the **Jobs** view: 11 tidy columns, title first, instead of every raw field. ### Pricing **$2 per 1,000 jobs**, plus $0.01 per run. Closed-job rows and errors are free. With **Only jobs that are new since the last run**, a daily schedule only pays for the new ones. ### For AI agents For a fast answer call with `{"searches": ["software engineer"], "maxJobsPerSearch": 20, "includeDescription": false}` — a few seconds. The defaults (up to 200 jobs with full descriptions) can take about a minute, which is longer than many agent tool timeouts. Each row has `type`: `job`, `closed` or `error`. `isNewSinceLastRun: null` means "no previous run to compare with". **Same filters on every site (10/2026):** experience level (read from the title: intern → executive, returned as a `seniority` column) and employment type (the site's own words normalised into full-time / part-time / contract / temporary / internship, returned as `employmentTypes`). They only narrow what is returned — no extra requests, no extra cost. **Zero rows is never ambiguous.** The run's status message says why, per search — e.g. `"zzz": no results on the site`, `results found but all removed by your filters` or `nothing new since the last run` — and the `OUTPUT` record in the run's key-value store has the same as JSON: `perSearch[].status` is `ok`, `no-results`, `all-filtered`, `nothing-new` or `error`, with `listed`, `read`, `returned`, `new` and `closed`. Set `summaryRows: true` to get it as free `type: "summary"` rows instead. **Same core columns on every northbell job scraper** (15 job sites + 10 company-career-page scrapers), so you can stack them into one table: `jobId`, `title`, `company`, `location`, `countryCode` (ISO, job sites), `remote` (true / false / null), `employmentType` (the site's own words), `postedAt`, `jobUrl`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval`, `isNewSinceLastRun`. Unknown is `null`, never a guess. ### More job scrapers from northbell Job sites: [SEEK](https://apify.com/northbell/seek-jobs-scraper) · [JobStreet](https://apify.com/northbell/jobstreet-jobs-scraper) · [JobsDB](https://apify.com/northbell/jobsdb-jobs-scraper) · [Instahyre](https://apify.com/northbell/instahyre-jobs-scraper) · [Reed](https://apify.com/northbell/reed-jobs-scraper) · [InfoJobs](https://apify.com/northbell/infojobs-jobs-scraper) · [XING](https://apify.com/northbell/xing-jobs-scraper) · [Dice](https://apify.com/northbell/dice-jobs-scraper) · [HelloWork](https://apify.com/northbell/hellowork-jobs-scraper) · [Computrabajo](https://apify.com/northbell/computrabajo-jobs-scraper) · [Foundit](https://apify.com/northbell/foundit-jobs-scraper) · [jobs.ch](https://apify.com/northbell/jobs-ch-scraper) · [jobup.ch](https://apify.com/northbell/jobup-ch-scraper) · [Arbeitsagentur](https://apify.com/northbell/arbeitsagentur-jobs-scraper) · [Arbeitnow](https://apify.com/northbell/arbeitnow-jobs-scraper) · [Visa Sponsorship Jobs](https://apify.com/northbell/visa-sponsorship-jobs-scraper). Company career pages with exact new/closed tracking: [Greenhouse](https://apify.com/northbell/greenhouse-jobs-scraper) · [Lever](https://apify.com/northbell/lever-jobs-scraper) · [Workday](https://apify.com/northbell/workday-jobs-scraper) · [AI companies](https://apify.com/northbell/ai-jobs-scraper). # Actor input Schema ## `searches` (type: `array`): One search per line, the same words you would type on Dice — e.g. "software engineer". Many searches in one run cost one start fee. ## `startUrls` (type: `array`): Or paste search result URLs from Dice — set any filters on the site first, then copy the address, e.g. undefined. Each URL is its own search. ## `location` (type: `string`): Same as the "where" box on Dice, e.g. "Texas". Leave empty for the whole country. ## `postedWithinDays` (type: `integer`): Only jobs posted in the last N days. Leave empty for all. ## `radiusMiles` (type: `integer`): Only with a Location. Dice uses 30 miles when empty. ## `output` (type: `string`): Schedule this Actor daily and pick "Only new" to get a cheap new-jobs feed. The first run returns everything (there is nothing to compare with yet). ## `summaryRows` (type: `boolean`): Adds one free row with type "summary" per search: status (ok / no-results / all-filtered / nothing-new / error), listed, read, returned, new, closed. Off by default so your job table stays clean; the same summary is always in the run status message and the OUTPUT record. ## `titleKeywords` (type: `string`): Comma-separated. Keep jobs whose title contains any of these, e.g. "senior, lead". ## `locationKeywords` (type: `string`): Comma-separated. Filters the returned jobs by their location text. ## `experienceLevels` (type: `array`): Keep only these levels, read from the job title (the same words on every northbell job scraper; each row also gets a seniority column). Product, account and other non-people "managers" count as mid level. ## `employmentTypes` (type: `array`): Normalised from the site's own words (Vollzeit, CDI, Jornada completa, workload %, …) into the same five types on every site; each row also gets an employmentTypes column. Roles whose type is not stated are left out when you set this, and counted in OUTPUT. ## `withSalaryOnly` (type: `boolean`): Keep only jobs whose salary could be read as a number. ## `remoteOnly` (type: `boolean`): Keep only jobs the site marks as remote. ## `includeDescription` (type: `boolean`): The complete job text as plain text. One extra request per job returned (only the jobs you keep after filtering). Turn off for faster runs. ## `trackChanges` (type: `boolean`): Remembers which jobs each search returned, so the next run can mark new ones (and closed ones, when the whole search fits in Max jobs). ## `maxJobsPerSearch` (type: `integer`): Caps what you pay for: $2 per 1,000 jobs. Newest first on Dice. ## Actor input object example ```json { "searches": [ "software engineer", "data" ], "output": "all", "summaryRows": false, "withSalaryOnly": false, "remoteOnly": false, "includeDescription": true, "trackChanges": true, "maxJobsPerSearch": 50 } ``` # Actor output Schema ## `all` (type: `string`): No description ## `jobs` (type: `string`): No description ## `summary` (type: `string`): No description # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "searches": [ "software engineer", "data" ], "maxJobsPerSearch": 50 }; // Run the Actor and wait for it to finish const run = await client.actor("northbell/visa-sponsorship-jobs-scraper").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "searches": [ "software engineer", "data", ], "maxJobsPerSearch": 50, } # Run the Actor and wait for it to finish run = client.actor("northbell/visa-sponsorship-jobs-scraper").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 '{ "searches": [ "software engineer", "data" ], "maxJobsPerSearch": 50 }' | apify call northbell/visa-sponsorship-jobs-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,northbell/visa-sponsorship-jobs-scraper" } } } ``` 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 ` 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/nLmtqmpkfoXrTNsHw/builds/ZDFBi1xHlEKkLuOK5/openapi.json