# Remote Jobs Worldwide · 8 Boards, One Schema (`bibian/remote-jobs-worldwide-scraper`) Actor Extract remote job postings from 8 major remote-work boards in one run: RemoteOK, Remotive, We Work Remotely, Jobicy, Working Nomads, Hacker News Who is Hiring, Wellfound and Get on Board. One unified schema, deduplicated across sources, no login. - **URL**: https://apify.com/bibian/remote-jobs-worldwide-scraper.md - **Developed by:** [Vivien MORVAN](https://apify.com/bibian) (community) - **Categories:** Jobs - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.96 / 1,000 job postings 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 ## Remote Jobs Worldwide · 8 Boards, One Schema Extract remote job postings from 8 major remote-work boards in a single run — [RemoteOK](https://remoteok.com), [Remotive](https://remotive.com), [We Work Remotely](https://weworkremotely.com), [Jobicy](https://jobicy.com), [Working Nomads](https://www.workingnomads.com), [Hacker News "Who is Hiring"](https://news.ycombinator.com), [Wellfound](https://wellfound.com) and [Get on Board](https://www.getonbrd.com) — mapped to one unified schema, deduplicated across sources. No login, no browser to configure. ### What you can do with it - **Search remote jobs across tech, sales, design and ops in one run**, instead of buying and maintaining 8 separate scrapers. - **Filter once, everywhere**: `keywords` and `region` apply the same way across all 8 sources. - **Compare pay across boards**: every record shares the same `salaryMin`/`salaryMax` and `employmentType` fields, whichever site it came from. - **Monitor new postings daily**: schedule it with `onlyNew` checked and `publishedWithinDays: 1` to get, and pay for, only what is new since the last run. ### Input | Field | What it does | |---|---| | `keywords` | Job title, skill or trade, for example `backend engineer`. Empty means every posting. | | `region` | Keep only postings open to this part of the world: `anywhere`, `europe`, `americas`, `asia`, `africa` or `oceania`. Best effort, based on whatever location the source itself publishes. | | `location` | City or region text, used only by the sources that support it; ignored by the others. | | `sources` | Which of the 8 remote job boards to query in this run. Defaults to all 8. | | `publishedWithinDays` | Keep only postings published in the last N days. Use `1` for a daily monitoring run. | | `maxItems` | The run stops once this many postings are saved, across all sources combined (default 50). | | `includeDescriptions` | Add the job description as plain text (off by default, for a fast run). | | `onlyNew` | For scheduled runs: skip postings an earlier run of this same search already delivered. | ### Output One record per posting, in the schema shared by every job actor on this account: | Field | Type | Meaning | |---|---|---| | `id` | string | Stable identifier (`:`), used to deduplicate between runs. | | `url` | string | Public page of the posting. | | `title` | string | Job title as published. | | `companyName` | string or null | Employer name; `null` when hidden (then `confidentialCompany: true`). | | `companyUrl` | string or null | Company page on the source site, when it exists. | | `locationLabel` | string or null | Location or region as displayed by the site. | | `city` / `region` / `postalCode` | string or null | Finer location breakdown, when the site publishes one. | | `country` | string or null | ISO 3166-1 alpha-2 country code of the employer, when published. `null` when the posting carries no country (common for worldwide-remote roles) — the only job pack on this account where `country` is allowed to be empty. | | `remote` | string | Always `remote`: every source in this pack is a remote-only board. | | `employmentType` | string | `full_time`, `part_time`, `contract`, `freelance`, `internship`, `apprenticeship`, `temporary` or `unknown`. | | `salaryMin` / `salaryMax` | number or null | Salary range, as numbers. | | `salaryCurrency` | string or null | ISO 4217 currency code. | | `salaryPeriod` | string or null | `hour`, `day`, `month` or `year`. | | `datePosted` | string or null | Publication date, ISO 8601. | | `validThrough` | string or null | Expiry date, ISO 8601. | | `description` | string or null | Plain-text description, only when `includeDescriptions` is on. No personal data. | | `experienceLevel` | string or null | As named by the site. | | `industry` | string or null | As named by the site. | | `skills` | string\[] | Skills listed by the site, if any. | | `source` | string | Host name of the source site. | | `sourceId` | string | Native identifier on the source site. | | `scrapedAt` | string | Extraction timestamp, ISO 8601. | Site-specific fields are kept in addition to these (never in place of them) — for example Jobicy's raw `geo` tag, RemoteOK's `tags`, or Wellfound's role slug. ### Why this one 8 of the biggest remote-work boards in one run, one schema, deduplicated between sources — the same posting cross-listed on RemoteOK and We Work Remotely only counts once. `source` on every row to filter or split by board. `region` to narrow a worldwide run without hunting for the right site. No connection, no login, no browser to configure, no recruiter e-mail ever included. ### Good to know - `region` is a best-effort filter: most remote boards publish a free-text location, not a structured continent field, so an unclear or missing location is kept rather than dropped. - `employmentType` is read from each site's own field when it has one; when a source carries none, it is inferred from the title and description, and left `unknown` rather than guessed when nothing matches. - Every result is deduplicated across all 8 sources before it is counted or charged. - No personal data: contact details of individuals are stripped from descriptions; only companies are named. # Actor input Schema ## `keywords` (type: `string`): Job title, skill or trade, for example "backend engineer" or "product designer". Leave empty to get every posting. ## `region` (type: `string`): Keep only postings open to this part of the world (best effort, based on whatever location the source itself publishes). "Anywhere" keeps every posting. ## `location` (type: `string`): City or region text, used only by the sources that support it; ignored by the others. ## `sources` (type: `array`): Remote job boards to query in this run. ## `publishedWithinDays` (type: `integer`): Keep only postings published in the last N days. Use 1 for a daily monitoring run. Leave empty for no limit. ## `maxItems` (type: `integer`): The run stops once this many postings are saved, across all sources combined. ## `includeDescriptions` (type: `boolean`): Add the job description as plain text. Off by default to keep the default run fast. ## `onlyNew` (type: `boolean`): For scheduled runs. Skip the results that an earlier run of this same search already delivered, so each run returns, and charges, only what is new. The memory is kept in the key-value store "only-new-memory-bibian" of your account. ## Actor input object example ```json { "keywords": "engineer", "region": "anywhere", "sources": [ "remoteok", "remotive", "weworkremotely", "jobicy", "workingnomads", "hackernews", "wellfound", "getonbrd" ], "maxItems": 50, "includeDescriptions": false, "onlyNew": false } ``` # Actor output Schema ## `postings` (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 = { "keywords": "engineer", "location": "", "maxItems": 50 }; // Run the Actor and wait for it to finish const run = await client.actor("bibian/remote-jobs-worldwide-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 = { "keywords": "engineer", "location": "", "maxItems": 50, } # Run the Actor and wait for it to finish run = client.actor("bibian/remote-jobs-worldwide-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 '{ "keywords": "engineer", "location": "", "maxItems": 50 }' | apify call bibian/remote-jobs-worldwide-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,bibian/remote-jobs-worldwide-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/kOLM3UuCiZvdHDgq5/builds/e2uHv1LXUGZk4oyPH/openapi.json