We Work Remotely Jobs Search Scraper
Pricing
from $2.99 / 1,000 we work remotely remote job records
We Work Remotely Jobs Search Scraper
Scrape remote job listings from We Work Remotely, the largest remote work community. Extract job titles, companies, locations, categories, and application details for remote recruitment and market analysis.
Pricing
from $2.99 / 1,000 we work remotely remote job records
Rating
0.0
(0)
Developer
Jobs API
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
We Work Remotely public jobs search scraper
This Actor extracts complete, detail-verified job records from public We Work Remotely pages.
Modes
searchdiscovers public/remote-jobs/<slug>links from the site search page and fetches each detail page.singleverifies one exact public detail URL.multipleverifies a list of exact public detail URLs.
The Actor uses ordinary HTTPS requests and parses public HTML and JobPosting JSON-LD. It does not log in, use a proxy, launch a browser, inject fingerprints, or emit diagnostic rows. Verified jobs survive unrelated detail failures with succeeded_with_limitations; a run with no verified jobs fails without dataset rows.
Example
{"mode": "search","query": "developer","maxItems": 3}
For direct verification, use the exact public detail URL fields shown in INPUT-single.json and INPUT-multiple.json. Optional values such as salary, locations, benefits, expiry, and application links are emitted only when the public posting supplies them.
Output guarantees
Every dataset item is a complete public job record with a stable URL slug, canonical detail URL, title, company, date posted, HTML and text description, and verification evidence. applyUrl is present only when the page exposes an explicit application link or action; the job URL is never used as a substitute.
maxRequests, requestTimeoutSecs, requestDelayMs, and maxItems bound public target access. RUN_SUMMARY and RUN_DIAGNOSTICS expose request, runtime, and failure evidence outside the dataset. Start with three records. Direct access is the default; opt-in proxyConfiguration is available for target-side environment blocking.