Remote jobs feed - 2,000+ company career sites, no board tokens
Pricing
from $5.00 / 1,000 records
Remote jobs feed - 2,000+ company career sites, no board tokens
Remote job postings from 2,099 verified company career sites on Greenhouse, Lever, Ashby and Workable. No board tokens to look up: the index ships inside the Actor. Filter by keyword, location, company and recency; each row says whether remote came from the ATS flag or the location text.
Pricing
from $5.00 / 1,000 records
Rating
0.0
(0)
Developer
RetrainMap Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Remote jobs feed — 2,000+ company career sites, no board tokens
Remote-flagged job postings read straight from companies' own applicant-tracking systems — Greenhouse, Lever, Ashby and Workable — across a bundled index of 2,099 verified company boards. You do not look up a single board token: run it empty and it walks the index, biggest board first, until it has as many remote jobs as you asked for.
These are the employers' own public, keyless job endpoints, so the rows are the postings as the company published them — title, department, location, employment type, posted date, apply link, description, and salary wherever the ATS carries one.
What makes this different from a job aggregator
| This Actor | A job-board scraper | |
|---|---|---|
| Source | The employer's own ATS API | A third-party listings site |
| Freshness | Whatever the company published, at run time | Whatever the aggregator last crawled |
| Apply link | The company's real application page | Often a redirect or a re-post |
| Terms | Public, keyless, documented endpoints | Usually against the site's terms |
Input
Everything is optional.
| Field | Meaning |
|---|---|
keyword | Substring in title / department / team / description (engineer, nurse) |
location | Substring in the posting's location(s) or country — remote roles are usually still region-limited |
max_records | Stop after this many remote rows (default 200) |
max_boards | How far down the index to walk (default 150, max 2,100) |
ats | Limit to some of Greenhouse / Lever / Ashby / Workable |
company_contains | Restrict the walk to matching company names or board slugs |
require_ats_flag | Keep only rows the ATS itself flagged remote (see below) |
posted_within_days | Only postings published in the last N days |
Empty input → the 150 biggest boards, up to 200 remote postings.
The remote flag, honestly
Lever, Ashby and Workable each publish a remote/workplace flag. Greenhouse does not. So for Greenhouse boards the flag is read from a "Workplace Type" metadata field when the company filled one in, and otherwise inferred from the word "remote" in the location text.
Every row carries remote_source:
ats_flag— the ATS declared it (LeverworkplaceType, AshbyisRemote, Workabletelecommuting)location_text— inferred from the location stringnone— no signal at all (these rows are never returned; onlyremote = truerows are)
Set require_ats_flag to drop everything that was inferred. The run summary reports how
many returned rows were inference-based.
Output
One row per posting:
ats · board · company · job_id · title · department · team · location · all_locations · country · remote · remote_source · workplace_type · employment_type · posted_at · updated_at · url · apply_url · description · salary_min · salary_max · salary_currency · salary_interval · salary_note · source_url · fetched_at · board_verified_atRUN_SUMMARY in the key-value store records the board index used, how many boards were read,
how many failed and why, request and byte counts, and the filters applied.
The board index
data/boards.csv, shipped inside the image: company, ATS, board slug, job count at
verification, and the timestamp it was verified. Every board in it answered with at least one
live posting when it was checked — it is the RetrainMap ATS index behind
retrainmap.com/data, not a guessed list of slugs. Companies
do leave an ATS; a board that has gone 404 is listed in RUN_SUMMARY.boards with its error
rather than dropped in silence.
When a run fails
If an ATS answers in a shape it does not document, the run stops with a SourceError
naming the endpoint. It never emits guessed rows. A single unreadable board is recorded and
the run continues; only every-board-failed is fatal.
Politeness and identification
One request per board, at most one request per request_interval_ms (250 ms floor), two
retries with back-off on 429/5xx. Every request identifies the operator by product-token
User-Agent and carries a contact address in the standard From: header (RFC 9110 §10.1.2).
Pricing
Pay per event: $0.10 per run start + $0.005 per job row.
Related: ATS jobs (the same normaliser for boards you name), Company hiring signals (which companies opened or closed the most postings since your last run), and the full 109,000-posting weekly dataset at retrainmap.com/data.
By Steelyard Ventures LLC (brand: RetrainMap) · info@steelyardclinical.com
