Remote Jobs Scraper: RemoteOK, Remotive, WWR, Himalayas avatar

Remote Jobs Scraper: RemoteOK, Remotive, WWR, Himalayas

Pricing

from $0.05 / 1,000 job results

Go to Apify Store
Remote Jobs Scraper: RemoteOK, Remotive, WWR, Himalayas

Remote Jobs Scraper: RemoteOK, Remotive, WWR, Himalayas

Recent remote jobs with complete original descriptions (text and HTML), locations, posting dates and source links. Filter by keywords, location, remote, job type and posting age. Only verified postings; repeats are suppressed. No login or API key.

Pricing

from $0.05 / 1,000 job results

Rating

0.0

(0)

Developer

Nomad.Devs

Nomad.Devs

Maintained by Community

Actor stats

0

Bookmarked

18

Total users

3

Monthly active users

2 days ago

Last modified

Share

Remote Jobs Scraper — RemoteOK, Remotive, WWR, Himalayas

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: actor-start $0.005; result $0.002. Scale and Business plans pay less per result event: $0.075 and $0.05 per 1,000.

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 jSM1JNEVLse0oadID (2026-10-03, immutable build ESEYIC6peh73hedwQ). This is an observed example, not a guarantee that repeating it returns this row. It used an earlier build; current-build execution has not been proved by this example.

Input JSON

{
"queries": [],
"locations": [],
"locationTypes": [],
"employmentTypes": [],
"postedWithin": "any",
"maxItems": 150,
"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": "himalayas",
"id": "35984e4a58366457ba9c3196f649b7e3ef2c2a84d3d8b0315f3bac1003a6c662",
"url": "https://himalayas.app/companies/crawford-company/jobs/payroll-specialist",
"title": "Payroll Specialist",
"company": "Crawford & Company",
"locations": [],
"postedAt": "2026-10-03T18:39:43Z",
"deadline": "2026-12-02",
"description": "Perform a variety of support tasks associated with payroll operations. Process wage and salary payments, audit time entries, and schedule garnishment payments. Calculate and process special checks, file unemployment forms, process new hire paperwork, and create summary reports for management. Utilize automated time and attendance software and programs in day… [truncated for display]",
"descriptionHtml": "<p>Perform a variety of support tasks associated with payroll operations. Process wage and salary payments, audit time entries, and schedule garnishment payments. Calculate and process special checks, file unemployment forms, process new hire paperwork, and create summary reports for management. Utilize automated time and attendance software and programs in … [truncated for display]",
"workType": "remote",
"salary": null,
"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 remote 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; 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 jobs from public job sources: Remote OK, Remotive and We Work Remotely; Himalayas. 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.

Input

{"schemaVersion": "nomad-agent-simple-inventory-search-v2", "queries": ["software engineer"], "locations": ["Europe"], "locationTypes": ["remote"], "employmentTypes": [], "postedWithin": "7d", "maxItems": 150, "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 150; 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-v4 format: schemaVersion, source, id, url, title, company, locations, 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. 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: 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: 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.

Fast setup and source code

Public repository · Agent setup skill.

Use the Actor’s current input form for filters, or start with its documented API example. Select latest for remote-boards-scraper and record the immutable build ID and number returned by your run. Inspect the dataset and any run summary the Actor documents together; a successful status alone does not establish complete source coverage.

Restrictive filters or repeat-delivery suppression can produce zero results. Diagnostics and demo records are not source records. Optional AI or translation stays explicit where supported.

Observed output example

Selected fields from a real source record inspected on 2026-10-03; consult the output schema for the full contract. Values change with the source.

{
"schemaVersion": "nomad-agent-job-row-v3",
"source": "remote_boards",
"id": "weworkremotely_6sense-manager-customer-success-upmarket",
"url": "https://weworkremotely.com/remote-jobs/6sense-manager-customer-success-upmarket",
"title": "Manager, Customer Success - Upmarket",
"company": "6sense",
"locations": [
"Anywhere in the World | 🇺🇸 United States of America"
],
"postedAt": "2026-10-02",
"deadline": "2026-11-01",
"workType": "remote",
"salary": null,
"employmentTypes": [
"Full-time"
],
"hiringContacts": []
}

Current costs

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

EventFreeBronzeSilverGoldPlatinumDiamond
Actor start (actor-start)$0.00005$0.00005$0.00005$0.00005$0.00005$0.00005
Job result (result)$0.0001$0.0001$0.000075$0.00005$0.00005$0.00005

For example, 1 × actor-start, 100 × result totals $0.205 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.