All Jobs Scraper (No Login) + 21 Boards in One

$0.2/1K jobs | Search 21 job boards in one run: tech, remote, European and research jobs, each with the complete original description, location, date and source link. Repeats are skipped across runs. No login or API key. Independent, unofficial tool. Not affiliated with or endorsed by the job boards and sites it reads.

All Jobs Bulk Scraper

Our scraper collects recent tech, remote, European and research jobs from 21 job boards in one run, and lets you filter by keyword, location, work arrangement, employment type and posting age. Every row carries the complete original description in text and HTML, plus the source link and the board it came from. It is ideal for job-aggregator back ends, market-wide hiring analytics and one-schedule alert feeds across many boards.

• Only need one niche? The topic bundles cut the noise: AI & ML Engineer Jobs Scraper (No Login) + 10 Boards for AI and ML roles, PhD, Postdoc & Research Jobs Scraper (No Login) + 11 Boards for PhD, postdoc and research jobs, Europe Jobs Scraper (No Login) + 14 Boards for European boards, American Jobs Scraper (No Login) + 8 US & Remote Boards for US and remote tech, and Web Developer Jobs Scraper (No Login) + 12 Boards for web and software developers. Each reads its own board list, mostly boards that are also in this Actor.
• Need only LinkedIn, searched deeply? Use LinkedIn Jobs Scraper (No Cookies) + Full Descriptions: LinkedIn is just one of the 21 boards here and a run can be limited or blocked on it.
• Need one board with its own source-specific filters? Use the single-board Actors such as Welcome to the Jungle Jobs Scraper (No Login) + Full Text, NoFluffJobs Scraper (No Login) + Full Descriptions, EURES Jobs Scraper (No Login) + Full Descriptions or Remote Jobs Scraper — RemoteOK, Remotive, WWR, Himalayas. They are narrower than this bundle.
• Need jobs straight from company career pages? See Company Careers Jobs Scraper (No Login) + 16 Employers; it is a different source set from the job boards here.
• Browse all our job-board scrapers: https://apify.com/nomad-agent

Key Benefits

• No login or API key: nothing to set up, no account of yours at risk, and no cookies to hand over.
• Low pricing: $0.20 per 1,000 jobs ($0.0002 per job), with lower rates on Scale and Business plans ($0.15 and $0.1 per 1,000), plus $0.00005 per run start.
• Full descriptions only: a posting with a missing or truncated description is never returned.
• 21 boards, one schema: every row is the same 15-field format, with source naming the board.
• No repeats across runs: schedule the same search daily and get only postings you have not received yet.

How It Works

1. Provide your search. Every filter is optional, and an empty list means no filter:
   • (optional) Search queries (e.g., software engineer). A posting matches when its title or description contains every word of a query, as whole words.
   • (optional) Locations (e.g., Europe, DE, Berlin). Countries match by name, code and native name, and EU and Europe cover their member countries.
   • (optional) Work arrangement (remote, hybrid, onsite) and employment type (Full-time, Part-time, Contract, Internship).
   • (optional) Posted within (e.g., 24h, 7d, 2w). Default is any.
2. Set how many jobs you want with maxItems.
3. Click Start. The form opens with software engineer in Europe and 20 jobs, and a 10-row test run of that search returned 10 rows, all with a full description.

More settings:

• maxItems - Maximum number of jobs per run. Default is 200; 0, or anything above 200, means 200.
• maxItemsPerSource - Caps how many postings each board contributes. Default is 50, at most 200. maxItems then keeps the newest postings across all boards.
• dedupe - On by default: postings already delivered to your Apify account for the same search are skipped. Set dedupe.enabled to false to get everything again, or set dedupe.key to keep separate alert histories.

Run the same search twice and the second run returns only new postings, possibly none. That is the repeat suppression working; turn dedupe off to see every posting again.

Coverage: Foorilla, Built In, Remote OK, Remotive, We Work Remotely, Hacker News (Who is hiring), Y Combinator Work at a Startup, Welcome to the Jungle, JustJoin.it, NoFluffJobs, InfoJobs, Tecnoempleo, EURES, EURAXESS, jobs.ac.uk, Ikerbasque, UN Careers, ReliefWeb, Impactpool and the University of Copenhagen (Mathematical Sciences) are served from verified postings, and LinkedIn is read live on every run. Each row keeps its own source.

LinkedIn can be limited or blocked during a run. When that happens its rows are fewer than requested or missing, the other boards are still returned, RUN-SUMMARY.unavailableSources names LinkedIn, and the run is marked partial.

When you set work arrangement or employment type, a posting whose source does not state that fact is left out. Salary and hiring contacts are filled only when the source publishes them (none of the 10 rows in our test run had either), so treat them as bonus fields.

Data You'll Receive

• Job details: title, complete description (text and HTML), locations, posting date, deadline (when published), work arrangement, employment types, salary (when published).
• Employer: company name.
• Links: original posting URL.
• Hiring contacts: the people a source names, when it names any (otherwise an empty list).
• Identity: source and a stable id, so you can deduplicate across runs.

Rows use the nomad-agent-job-row-v3 format, newest postings first. Unknown optional facts are null.

Sample output data

Here is an example job from this Actor (one row of our test run, description shortened):

{
  "schemaVersion": "nomad-agent-job-row-v5",
  "source": "justjoinit",
  "id": "agileengine-documentation-engineer-krakow-other",
  "url": "https://justjoin.it/job-offer/agileengine-documentation-engineer-krakow-other",
  "title": "Documentation Engineer",
  "company": "AgileEngine",
  "locations": [
    "Kraków, PL"
  ],
  "countryCodes": [
    "PL"
  ],
  "applicantLocations": null,
  "postedAt": "2026-10-13",
  "deadline": "2026-12-31",
  "description": "About the roleWe are looking for a Senior Technical Writer to design and automate AI-driven software documentation for end users, developers, and system integrators.The mandatory requirements are 4+ years of technical writing experience, prompt engineering and AI tools, APIs, systems and data models… [truncated for display]",
  "descriptionHtml": "About the roleWe are looking for a Senior Technical Writer to design and automate AI-driven software documentation for end users, developers, and system integrators.The mandatory requirements are 4+ y… [truncated for display]",
  "workType": "remote",
  "salary": null,
  "employmentTypes": [
    "Full-time",
    "Contract"
  ],
  "hiringContacts": []
}

All Jobs API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read on demand through the Apify API. A run summary, including any input field that was mapped or ignored, is written to the RUN-SUMMARY record of the run's key-value store.

Support and Feedback

We improve these scrapers from your feedback. If something breaks or you need a filter:

• Open an issue on the Actor's Issues tab
• If this Actor saved you time, a short review on the Store helps other users find it.

Run evidence

Start with one input and output

An Apify account is required. Use your Apify API token when calling the API; Console runs do not need that token pasted into the input. No user API-key field is required by this input schema.

Free-tier event rates checked 2026-10-04: result $0.0002; actor-start $0.00005.

Cost: Total = Actor event charges + platform usage if separately billed + any BYO-provider charges. See “Current costs” for your event rates, plan tiers and a calculation. A sample does not promise future billable volume.

Input and output below were read from the same successful run YTJgOwbd4CxP4a5Fj (2026-10-04, immutable build Llb2bAB2q135psAiR). This is an observed example, not a guarantee that repeating it returns this row.

Input JSON

{
  "queries": [],
  "locations": [],
  "locationTypes": [],
  "employmentTypes": [],
  "postedWithin": "any",
  "maxItems": 200,
  "maxItemsPerSource": 50,
  "dedupe": {
    "enabled": true,
    "key": ""
  },
  "schemaVersion": "nomad-agent-simple-inventory-search-v2"
}

Matching output excerpt

Long strings and arrays are shortened for display; this is not a complete dataset fixture.

{
  "schemaVersion": "nomad-agent-job-row-v3",
  "source": "ycombinator_was",
  "id": "103104",
  "url": "https://www.workatastartup.com/jobs/103104",
  "title": "Founding Design Engineer",
  "company": "Uplift AI",
  "locations": [
    "Lahore, Punjab, PK"
  ],
  "postedAt": "2026-10-03T07:00:00Z",
  "deadline": null,
  "description": "This Role You will own Uplift AI’s entire brand identity and the most challenging interface design projects. Like helping people annotate audio 10× faster without getting tired or distracted. Or making it easy for busy small-business owners to provide feedback that helps their voice AI agents improve themselves. What we do We build voice models and voice app… [truncated for display]",
  "descriptionHtml": "<h3>This Role</h3>\n<p>You will own Uplift AI’s entire brand identity and the most challenging interface design projects. Like helping people annotate audio 10× faster without getting tired or distracted. Or making it easy for busy small-business owners to provide feedback that helps their voice AI agents improve themselves.<br>\n<br>\n<strong>What we do</stron… [truncated for display]",
  "workType": null,
  "salary": "$1.5K - $2.5K / monthly",
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}

Retained dedupe history can suppress previously returned postings. Keep a stable key and save your own history; an unchanged rerun can return zero new rows.

Recent tech, remote, European and research jobs with complete original descriptions. Each row carries the source ID and URL, title, employer, locations, the original description as text and HTML, posting date, deadline, work arrangement, employment type, salary and the hiring contacts the source names, whenever the source publishes them. Unknown optional facts are null; an empty locations array means the source names no physical place, and an empty hiringContacts array means the source names nobody. locations is where the job is, countryCodes lists the countries of those places as ISO 3166-1 two-letter codes (null when no place has a known country), and applicantLocations is where an applicant may live, for example a remote job open only to residents of some countries: it is null when the source states nothing and [] when it states no restriction.

Coverage includes these public job sources: Foorilla Hiring (formerly aijobs.net); Built In; Remote OK, Remotive and We Work Remotely; Hacker News Who is hiring; Y Combinator's Work at a Startup; Welcome to the Jungle; JustJoin.it; NoFluffJobs; InfoJobs; Tecnoempleo; EURES; EURAXESS; jobs.ac.uk; Ikerbasque; UN Careers; ReliefWeb; Impactpool; University of Copenhagen (Mathematical Sciences). LinkedIn is also served, fetched live on every run. Each row keeps its own source. Every posting is verified before it is served. A posting with a missing, truncated or unverified description is never returned: every row has the full original text. LinkedIn results use the requested search filters. Each posting still has its full description or it is left out. LinkedIn may limit or block a run, so its rows can be fewer than requested or missing: the other boards are still returned, RUN-SUMMARY.unavailableSources names LinkedIn, and the run is marked partial.

Input

{"schemaVersion": "nomad-agent-simple-inventory-search-v2", "queries": ["software engineer"], "locations": ["Europe"], "locationTypes": ["remote"], "employmentTypes": [], "postedWithin": "7d", "maxItems": 200, "maxItemsPerSource": 50, "dedupe": {"enabled": true, "key": ""}}

Every filter is optional, and an empty list means no filter. Filters are applied to all available postings before maxItems is counted.

• queries: a posting matches a query when its title or description contains every word of it, as whole words, ignoring case. A posting matches when any query matches.
• locations: a city, region, country name or two-letter ISO country code. Countries match by name, code and native name (Germany, DE and Deutschland find the same postings), and EU and Europe cover their member countries.
• locationTypes (remote, hybrid, onsite) and employmentTypes (Full-time, Part-time, Contract, Internship): while one is set, a posting whose source does not state that fact is left out.
• postedWithin: a positive duration in hours (h), days (d), weeks (w) or 30-day months (m), up to 36500 days, or any. Postings without a source date use the date they were first seen, which later refreshes never reset.
• maxItems defaults to 200; 0, or anything above 200, means 200.
• maxItemsPerSource (default 50, at most 200) caps how many postings each source contributes; maxItems then keeps the newest postings across all sources.
• dedupe suppresses postings already delivered to the same Apify account for the same search; different filters keep separate histories. Set dedupe.enabled to false to get stateless results, or set dedupe.key to keep separate alert histories.

Output

One flat row per posting in the nomad-agent-job-row-v5 format: schemaVersion, source, id, url, title, company, locations, countryCodes, applicantLocations, postedAt, deadline, description, descriptionHtml, workType, salary, employmentTypes, hiringContacts. employmentTypes lists the types the source states (Full-time, Part-time, Contract, Internship) or is null. countryCodes lists the countries of the job's places as ISO 3166-1 alpha-2 codes (for example DE, FR), in the same order as locations, each once. A code comes from the source if it states one, otherwise from the place label. It's null when no place has a known country (a remote job with no country, or an unidentifiable place) and never an empty list. A place without a known country adds nothing, so the list can name fewer countries than there are places. A posting stored on a single-country board with no place at all carries that board's country, so locations can be [] while countryCodes names one. Postings read live from LinkedIn's public pages always have countryCodes: null. Those pages give a place label but no country code, so only stored postings carry a code. The locations filter matches countries against these codes as well as names and text. applicantLocations lists the regions where the source says an applicant may live (for example United States for a remote job open to US residents), null when it states nothing and [] when it states no restriction. Each hiring contact has a name, and a title and url or null. Newest postings come first. A run summary, including any input field that was mapped or ignored, is written to the RUN-SUMMARY record of the run's key-value store.

Changes

• October 2026: countryCodes added (row v5). Rows are now nomad-agent-job-row-v5: one new field, countryCodes, lists the ISO 3166-1 alpha-2 country codes of the job's places, in the order of locations, each once (null when no place has a known country, never an empty list). A code is the country the source states, or if it doesn't state one, the country read from the place label. A place whose country can't be determined adds nothing. Postings read live from LinkedIn carry null; its public pages show a place label but no country code. locations and applicantLocations are unchanged. Input, other fields, and pricing are unchanged. Integrations validating against the v4 schema must allow the new field and the new schemaVersion.
• October 2026: applicantLocations added (row v4). Rows are now nomad-agent-job-row-v4: one new field, applicantLocations, lists where an applicant may live as the source states it (null when the source states nothing, [] when it states no restriction). locations is unchanged and still the physical place only; for a remote job open to some regions it is often [] while applicantLocations lists the regions. Input, other fields and pricing are unchanged. Integrations that validate rows against the v3 schema must allow the new field and the new schemaVersion.
• October 2026: LinkedIn is read live. LinkedIn results reflect its current public job pages. Every row still has the complete description or is left out, and the other boards are unchanged. A LinkedIn failure no longer affects the other boards: the run is marked partial and RUN-SUMMARY.unavailableSources names it. Pricing is unchanged.
• October 2026: recordType removed. nomad-agent-job-row-v3 rows no longer include the recordType field, because every dataset row is a posting. Read schemaVersion instead. The RUN-SUMMARY record is unchanged.
• September 2026: search filters and richer rows. The input (nomad-agent-simple-inventory-search-v2) adds queries, locations, locationTypes and employmentTypes, and maxItemsPerSource (default 50). Rows are now nomad-agent-job-row-v3 and add employmentTypes and hiringContacts. Integrations that still send keyword or location keep working: those values become queries and locations, remote: true becomes locationTypes: ["remote"], and other old fields are ignored with a note in RUN-SUMMARY instead of failing the run. Pricing is unchanged.
• Earlier: this Actor moved to verified available postings in the shared simple job format, and every row includes the complete description.

Coding agents can use the public Actor setup skill for a first run, result checks and integration setup.

Product guides and related tools

• Guide and starter input on nomadagent.dev
• Product overview and public links
• Public setup guide
• Job Atlas job-data tools
• Oink personal job alerts
• Search ten job boards with one API call

Current costs

Current Actor event rates, checked 2026-10-16. USD; use the Pricing tab for your plan and later changes.

Event	Free	Bronze	Silver	Gold	Platinum	Diamond
Job result (result)	$0.0002	$0.0002	$0.00015	$0.0001	$0.0001	$0.0001
Actor start (actor-start)	$0.00005	$0.00005	$0.00005	$0.00005	$0.00005	$0.00005

For example, 100 × result, 1 × actor-start totals $0.02005 in Actor event charges on Free. This is an arithmetic example, before any waiver; actual charged events depend on the run and selected options. It is not a promise of output or a charge for simply setting an item cap.

Your total is the charged Actor events, plus platform usage only if this Actor’s Pricing tab bills it separately, plus any external provider you use with your own key. Do not add platform usage twice when it is included. Apify credits and plan discounts affect your invoice. Set a run cost limit in Console before starting.

---

Independent tool. We built and run this Actor ourselves. The job boards and sites it reads do not operate, sponsor or endorse it, and their names are used only to say where the data comes from.