Paste company career-page URLs and get every open job in one JSON format, whichever applicant tracking system the company uses: Greenhouse, Lever, Ashby, Workable, Recruitee, Teamtailor and more. $0.002 per job ($2 per 1,000), no start fee. Not affiliated with any ATS vendor.
README: removed the "How it compares" section (competitor Actors and their listed prices; Mike 2026-11-14). Links to our own Actors (Remote Jobs Aggregator, single-ATS Actors) are kept.
Copy (Lex's rules, Mike 2026-11-14): no 'official', 'monitor(ing)' or 'alert' wording left in README, .actor/actor.json or .actor/input_schema.json. 'Monitoring mode' is now 'only-new mode (onlyNewJobs)' on scheduled runs; the onlyNewJobs field title is 'Only new jobs' and the section caption 'Only-new runs and output'; 'Large monitoring run' reads 'Large scheduled run'; Polymer/HireHive are described as public APIs. Text only: no field name, default, prefill, price or output change. New guard test tests/test_1114_copy_words.py.
Files: README.md, .actor/input_schema.json, CHANGELOG.md, tests/test_1114_copy_words.py (new). No code change.
2026-11-14: clearer robots.txt-unreadable message
Fix (message only): a board skipped because its robots.txt could not be read (HTTP 429/5xx or timeout; the board is still skipped, as before) now reads robots.txt unreadable on <host>: HTTP 503 in RUN_SUMMARYboards[].error, in the demo/status item that quotes it, and in the log. Before, it read robots.txt disallows robots.txt unreadable on <host>: HTTP 503 and the log said robots.txt disallows access. Seen live 2026-11-14 9:07 AM ET, when utaustin.wd1.myworkdayjobs.com answered robots.txt with HTTP 503 ERR_TENANT_OUTAGE. A board that robots.txt really disallows keeps the same error text; its log line now names what is disallowed (<board>: robots.txt disallows <path>, skipped) instead of robots.txt disallows access, skipped. Same rule as remote-jobs-aggregator (robots_skip_reason).
No change to which boards are read or skipped, charging, prices, defaults, prefill, inputs or output fields.
2026-11-13: chain dataset readable under limited permissions (next build of 1.5)
Input schema:datasetId now declares "resourceType": "dataset" and "resourcePermissions": ["READ"] (editor stays textfield, field name and type unchanged). Apify then grants a limited-permissions run read access to the dataset given there. Fixes the chain run that failed with ForbiddenError ... Insufficient permissions on GET /v2/datasets/<id> (2026-11-13 cloud smoke of career-site-jobs-feed 0.3.1). The field description now says so and suggests {{resource.defaultDatasetId}} for integrations.
Code (my_actor/jobschema.py): reads the dataset through the declared datasetId field as before; the integration payload resource.defaultDatasetId fallback is kept. When the dataset cannot be read, the error message now says which of the two it came from, and for the payload it says to put {{resource.defaultDatasetId}} in datasetId. Same error type, same point in the run, nothing fetched or charged.
README: "Chain with other jobs Actors": datasetId row mentions {{resource.defaultDatasetId}}; one new bullet on read-only access under limited permissions.
No change to output, charging, prices, defaults, prefill or runs without datasetId.
2026-11-13: README rebased onto live 1.4.1
README only. Related Actors lines already matched live. Restored the live How-it-compares factpipe/ats-jobs-feed price line ($0.005 free plan / $0.0045 Bronze (lower on higher plans); the pack had $0.003 free plan / $0.0027 paid). The "Chain with other jobs Actors" section is unchanged. No code, schema, input or price change.
2026-11-11: chain with other jobs Actors (datasetId), shared job format (version 1.5)
New optional inputs datasetId, datasetMode, datasetMatchBy, suiteOutput (input-schema section "Chain with other jobs Actors (advanced)", no schema defaults, no prefill). Without them the run is unchanged: same items, same field order, same values, same charging, same RUN_SUMMARY keys (checked against golden output recorded from version 1.4 in tests/fixtures/suite_golden_current.json).
datasetId: job items of that dataset are read (in pages, at most 100,000 items) before any board; a job already there (by uid, or also by crossSourceKey with datasetMatchBy "uidOrCrossKey") is dropped before the push and never charged. datasetMode "merge" (default) copies the earlier job items first, free (pushed without an event name); "exclude" copies nothing. Status items and expired/unresolved records are not copied. Falls back to the Apify integration payload resource.defaultDatasetId when datasetId is empty. maxTotalJobs counts only new jobs.
Unreadable datasetId, unknown datasetMode or datasetMatchBy: the run fails with an input error before any board is read (as for other invalid input).
suiteOutput: true: each job item is rewritten into the shared field order (my_actor/jobschema.py, SUITE_FIELDS), with missing shared fields as null or []; values unchanged; jobs copied from datasetId are kept as they were. Off by default.
RUN_SUMMARY gets previousDataset (only when datasetId is used) and suiteOutput (only when true).
New shared file my_actor/jobschema.py (JSON Schema jobs-suite/1, byte-identical in all four jobs Actors). Tests: tests/test_1111_suite_contract.py, tests/test_1111_suite_chain.py, tests/suite_mock.py, fixtures jobs-suite-item.schema.json, suite_golden_current.json, suite_shared.sha256.json.
README: section "Chain with other jobs Actors". No change to prices, requirements.txt (apify >= 4.1, < 4.2), the Dockerfile, exampleRunInput or the prefill.
2026-11-11: remote boards take turns under maxTotalJobs, full Workday sample, jobicyTag wording, Jobicy 100 per request (version 1.4)
Behaviour change: remote boards take turns when they share a maxTotalJobs cap. Before, each remote board pushed as soon as it was read, so with remoteBoards: ["remoteok", "jobicy"], a maxTotalJobs cap and no maxJobsPerCompany, the board that answered first could fill the whole cap and the other got nothing (shown by a mock test where Jobicy answers 0.3 s later: 1.3 pushed 8 Remote OK jobs and 0 Jobicy jobs). Now the boards take turns in remoteBoards order: a board pushes a job only on its turn, and keeps the turn until it pushes one. Each board's jobs stay in its own feed order (they are not re-sorted).
A job dropped before the push (keyword, location, date and other filters, onlyNewJobs, newOnlyBy, excludeAgencies, salary and job filters, dedupeBy) never uses a turn. When a board finishes, fails, or reaches maxJobsPerCompany, it leaves the rotation and the other fills the rest. When the run stops (cap, cost limit, time budget, abort), every waiting board is released.
Turns apply only with maxTotalJobs set and two remote boards read in the run (Jobicy deferred by its hourly rule = one board). Without a cap, with one remote board, or for companies boards, pushing is unchanged. A board joins the rotation when its worker starts; the first board to join takes the first turn (normally the first in remoteBoards). With maxConcurrency 1 the second board cannot start before the first finishes, so turns cannot help there.
Side effect: a board waits for the other board's turn, so a slow board (its feed request still running) delays the other board's pushes. Waits are bounded by the request timeouts and the run's time budget.
dedupeBy semantics unchanged (job: the first copy read wins; companyTitle: merged per board). With dedupeBynone (the default) cross-posted copies are all kept; checked by a new test (ats does not have remote-jobs-aggregator's dedupe: false bug).
README Workday sample: the UT Austin item now has every field this Actor outputs for a Workday job with the default input, in output order, except descriptionText (removed, as the caption says). Added: expiresAt null, postedAtPrecision "day", workArrangement null, seniority "manager", dedupeKey, crossSourceKey, firstSeenAt, lastSeenAt (isAgency was added in 1.3). The added values were computed by running this Actor's own finalize() on the real item and its real description at the run's time; dedupeKey and crossSourceKey equal the real run's values. Caption rewritten to say exactly that. README remote-boards notes describe the turns.
jobicyTag wording: README and input-schema description now say what Jobicy's own API docs say about tag (keyword search; the API page says job title, the OpenAPI spec 2.2.19 says available job content, 3-50 characters ASCII). Code unchanged.
Behaviour change: Jobicy is asked for 100 jobs per request, not 200 (count=100 in my_actor/remote.py). 100 is the stricter documented limit: Jobicy's API page (jobs-rss-feed) says count accepts 1-100 and defaults to 100; its OpenAPI spec 2.2.19 says 1-200. Paging is unchanged: the adapter follows nextCursor with the same filters while hasMore is true, for at most 50 requests, so caps above 100 are still reached through cursor pages when Jobicy has enough matching jobs. Effects: the most Jobicy jobs one run can read drops from 10,000 (50 x 200) to 5,000 (50 x 100); reading more than 100 Jobicy jobs now takes twice as many requests (e.g. 300 jobs: 3 requests instead of 2). Only runs with remoteBoards including jobicy are affected; runs that read at most 100 Jobicy jobs make the same single request. ATS boards and Remote OK unchanged.
Tests: new tests/test_1111b_remote_turns.py (starvation guard with a slow board, remoteBoards order, empty and short boards, filters and dedupeBy job before the turns, dedupeBy none keeps cross-posted copies, maxJobsPerCompany still applies, turns only when needed, unit test of the rotation), tests/test_1111b_readme_workday_sample.py (README sample key set and order equal this Actor's Workday output with the default input, minus descriptionText). tests/test_1111_jobicy_tag.py expects count 100. New tests/test_1111b_jobicy_paging.py (fake Jobicy: 100 per page, cursor pages keep the filters, 50-page / 5,000-job limit, a maxTotalJobs 150 and a maxJobsPerCompany 250 reached through cursor pages).
.actor/actor.json version is 1.4. No change to prices, requirements.txt (apify >= 4.1, < 4.2), the Dockerfile, exampleRunInput or the prefill.
2026-11-11: example cleanup, jobicyTag documented, isAgency in the Workday sample (version 1.3)
User-visible error text: the two Workday ValueError messages (an entry without a full career-site URL; Workday rejecting the site name with HTTP 404/422) now give https://utaustin.wd1.myworkdayjobs.com/UTstaff as the example URL instead of the previous large-tenant career-site URL. Same conditions, same rest of the message; only the example URL changed.
Code comments and docstrings in my_actor/main.py and my_actor/sources.py use neutral examples (2100 Initech USA -> Initech USA; Pfizer's Allow: /PfizerCareers/). No behaviour change.
jobicyTag documented (README input table and remote-boards notes, and a new jobicyTag field in .actor/input_schema.json: type string, text field, no default, no prefill). Verified in my_actor/remote.py: it is one of REMOTE_OPTION_KEYS; a non-empty value is passed unchanged to Jobicy's API as tag, only when remoteBoards includes jobicy; an empty value is not sent; this Actor does not filter on it. The code path is unchanged; the input already worked from the API (it was "API only" since the 2026-11-10 remote-boards entry). Side effect of the schema entry: the field now shows in the Console form, and the platform's input validation now expects a string, so a non-string jobicyTag sent through the API would be rejected by the platform before the run starts.
README: the UT Austin Workday sample item now has "isAgency": false. That value is this Actor's agency.is_agency run locally on the real item (with its real description) from workday-jobs-scraper smoke run ilpMFiKmQhVUMdH3B; the caption says so. The sample still omits other fields this Actor adds (see the handoff note).
Remote boards (remoteBoards): no change. Their jobs are pushed as each board is read (one worker per board), not merged into one newest-first list, so the remote-jobs-aggregator turn-order fix does not apply here.
Tests (no behaviour change): the previous large-tenant examples replaced in tests/test_1103_tester.py, tests/test_gap11_duplicates_locations.py, tests/test_lookup_and_names.py, tests/test_merge_ports.py, tests/test_workday_hosts.py, tests/test_workday_nodesc.py, tests/test_workday_robots.py, tests/test_robots_live_path.py, tests/test_workday_facet_split.py. The old real-tenant fixture tests/fixtures/<tenant>.wd5.robots.txt is replaced by the synthetic tests/fixtures/acme.wd5.robots.txt with the same rule shapes. Mocked tests use acme / Initech / utaustin examples. The two live robots tests now use UT Austin UTstaff. The two live tests that need a very large site (facet split past 2,000 jobs; 20 remote multi-location jobs without descriptions) now read their site from WORKDAY_LIVE_FACET_URL / WORKDAY_LIVE_NODESC_URL and are skipped when unset. All live tests are still skipped with WORKDAY_LIVE_TESTS=0.
tests/test_1110_nowwr.py: the comparison with the 1.1.1 _base/ tree is now skipped with a clear reason when _base/ is not a sibling folder (a bare Actor tarball); when _base/ is present it runs unchanged. New tests/test_1111_jobicy_tag.py.
Older CHANGELOG entries are not rewritten; they still name the previous example company as history.
.actor/actor.json version is 1.3. No change to prices, requirements.txt (apify >= 4.1, < 4.2), the Dockerfile, exampleRunInput or the prefill.
Changed files: .actor/actor.json, .actor/input_schema.json, CHANGELOG.md, README.md, my_actor/main.py (comment only), my_actor/sources.py, the test files listed above, tests/fixtures/acme.wd5.robots.txt (new), the old wd5 real-tenant robots fixture (removed), tests/test_1110_nowwr.py, tests/test_1111_jobicy_tag.py (new).
2026-11-10: We Work Remotely removed (version 1.2)
We Work Remotely is no longer fetched. Its API terms forbid building a job search service. The board was removed from the live adapters in my_actor/remote.py (FEEDS / REMOTE_BOARDS are now remoteok and jobicy only). The Remote OK and Jobicy adapters are unchanged (function bodies byte-identical to 1.1.1).
If a saved input or schedule still lists weworkremotely in remoteBoards, the run does not fail and is not turned into the Airbnb demo. That name is ignored, one free status item explains the terms reason, and RUN_SUMMARY records removedRemoteBoards plus a board entry with status: "removed". Any other requested boards still run. weworkremotely stays in the input-schema enum (titled "We Work Remotely (no longer read)") so old Console inputs are not rejected. wwrCategories is kept and documented as unused.
README: starts from Echo's 10 Nov 2026 ats-remoteboards draft (already dropped WWR as a current source), plus the earlier docs items (no NVIDIA example URLs; Jobicy named state store ats-jobs-scraper-state / remote-jobicyLastPass; Remote Jobs Aggregator is the cheaper remote-only option at $0.001 vs $0.002), plus a short note that a saved weworkremotely value is ignored.
.actor/actor.json version is 1.2. Prefill and exampleRunInput are unchanged (Airbnb, 4 jobs). No price change.
2026-11-10 (actor.json version unchanged: 1.1; local stage 1110-ats-docs, not built)
Docs only: README and the companies field description in .actor/input_schema.json no longer use NVIDIA Workday example URLs. They now use https://utaustin.wd1.myworkdayjobs.com/UTstaff (and utaustin/UTstaff as the Workday slug example). The Workday sample item is real output from workday-jobs-scraper 1.1.1 smoke run ilpMFiKmQhVUMdH3B on 10 November 2026. Old CHANGELOG entries are unchanged.
Docs only: the remoteBoards README row now says that choosing Jobicy opens the named key-value state store (stateStoreName, default ats-jobs-scraper-state) and records the last pass under remote-jobicyLastPass, to enforce Jobicy's limit of one pass per hour even when monitoring options are off.
The README line that Remote Jobs Aggregator is the cheaper remote-only option ($0.001 per job versus $0.002 in this Actor) is unchanged.
No code, pricing, input defaults, prefill, or behaviour change. actor.json version stays 1.1 (Ranger's docs-only procedure: no actor.json version bump; the build patch number increments on push).
2026-11-10: 64 MB cap on the remote-board path, RJA price note (version 1.1)
Remote-board body cap: a remote-board response larger than 64 MB is streamed and dropped (BodyTooLarge), the same behaviour as remote-jobs-aggregator GAP12 (MAX_BODY_BYTES = 64 * 1048576 in my_actor/remote.py; Http._send in my_actor/sources.py). The cap is passed per request on the remote path only, so ATS company-board requests stay uncapped (default Http.max_bytes = 0). Remote boards never run in the ats demo, so there is no 16 MB demo cap. An oversized board is recorded as status: "error" and does not kill the run (BodyTooLarge is a ValueError, already caught in scrape_target).
README: one line that Remote Jobs Aggregator is the cheaper remote-only option ($0.001 per job versus $0.002 in this Actor). Both prices checked against Ranger's 10 Nov 2026 listing inspect (eventPriceUsd) and pricing_audit_20261102.json.
Contact redaction: the stronger phone removal stays on for every ATS job. New tests show salaries ($120,000-$150,000, 120k, €65.000), requisition IDs (R-123456, REQ 2024-00123, JR0012345), dates (2026-11-10, 11/10/2026, Nov 10, 2026) and years are not stripped. The regex was not changed.
robots.txt and terms (fetched 10 Nov 2026, 2:25 PM EST, plain GET, logged out, UA ATSJobsScraper/1.0): Remote OK, We Work Remotely and Jobicy are all kept. robots.txt allows every path this Actor uses. Terms require attribution / official-API fair use (one Jobicy pass per hour, already enforced); none ban this access. Evidence is in the staging folder, not in this Actor.
Tests: tests/test_1110_body_cap.py (new), tests/test_1110_redact_keeps.py (new). One assertion in tests/test_1110_jobsfeed.py (test_remote_http_follows_redirects_hop_by_hop_and_drops_params) now also expects max_bytes=64 MiB on each hop. No other existing test was changed.
Changed files: CHANGELOG.md, README.md, my_actor/remote.py, my_actor/sources.py, tests/test_1110_jobsfeed.py (two assertion lines), tests/test_1110_body_cap.py (new), tests/test_1110_redact_keeps.py (new). No change to .actor/actor.json (version stays 1.1), input/dataset/output schemas, requirements.txt (apify >= 4.1, < 4.2), the Dockerfile or prices.
2026-11-10: remote job boards, crossSourceKey, new-only by uid or crossSourceKey (version 1.1)
New input remoteBoards (default empty, so runs without it are unchanged): also read Remote OK, We Work Remotely (RSS) and Jobicy in the same run. The adapters are remote-jobs-aggregator's feeds.py (live 1.0.14), ported to my_actor/remote.py; requests go through this Actor's client (robots.txt on every host and every redirect hop, per-host delay, retries). Feed options use remote-jobs-aggregator's input names: wwrCategories, jobicyGeo, jobicyIndustry (in the form) and jobicyTag (API only, as in remote-jobs-aggregator).
Charging: remote-board jobs are pushed with the same job event as ATS jobs (Actor.push_data(..., charged_event_name='job'), unchanged code path). No new event. Free records (status, unresolved, expired) stay free.
Remote-board records: uid is source:id (the uid remote-jobs-aggregator gives the same job), ats is the board name, companySlug is null, and they keep source, sourceName, attribution, category, tags, companyLogo, expiresAt from the feed. A structured salary is labelled salarySource: "ats" like every structured salary in this Actor (remote-jobs-aggregator calls it "source"). No company-name lookup request is made for them. Contact redaction (redactContacts, default on) applies to them as to ATS jobs.
Remote boards run in the same worker pool as companies (maxConcurrency). maxJobsPerCompany caps jobs per remote board. With remote boards and no companies, the run is a normal run, not the demo (and the prefilled sample input is not treated as the demo when remote boards are added).
Jobicy fair use (one pass per hour): the last pass time is kept in the state store under remote-jobicyLastPass; the store is opened when jobicy is asked for even without monitoring options. A run within an hour of the last pass skips Jobicy with board status deferred (not counted as a failure); if nothing else is read, one free status item is written, so the dataset is never empty.
New output field crossSourceKey on every job record: sha1 of company (legal form at the end of the name removed) and title, no location, first 20 hex characters; null when the company name or title is empty. Recipe in my_actor/jobkey.py, byte-identical in workday-jobs-scraper and remote-jobs-aggregator.
dedupeKey now comes from jobkey.dedupe_key (enrich.py, dedupe.py). Same recipe; values unchanged (frozen vectors in tests/fixtures/jobkey_vectors.json).
New input newOnlyBy (used only with onlyNewJobs): uid (default, the behaviour so far) or uidOrCrossKey, which also skips a job whose crossSourceKey was output by an earlier run with that option on. Those keys are saved under SEEN_XKEY in the state store (120-day TTL, refreshed when seen again); with the default nothing is read from or written to SEEN_XKEY. Skipped jobs are never pushed or charged; boards get skippedSeenCrossKey and RUN_SUMMARY gets newOnlyBy and skippedSeenCrossKey (only with the option on). RUN_SUMMARY gets remoteBoards only when remote boards were asked for.
Input checks: an unknown remoteBoards name, a non-list value or an unknown newOnlyBy fails the run before any request with the usual "Invalid input, nothing was fetched or charged" message.
Contact redaction: phone numbers written with a bracketed area code and two groups, e.g. (555) 123-4567 or +1 (555) 123-4567, are now removed too (they were kept before). Numbers with fewer than 8 digits and dates are still kept.
README: API example uses /v2/actors/ from one APIFY_API variable; rows for crossSourceKey, remoteBoards, remote options and newOnlyBy; one pricing line for remote-board jobs.
Changed files: .actor/actor.json (version 1.1), .actor/input_schema.json, CHANGELOG.md, README.md, my_actor/dedupe.py, my_actor/enrich.py, my_actor/jobkey.py (new), my_actor/main.py, my_actor/remote.py (new), tests/fixtures/jobkey_vectors.json (new), tests/test_1110_jobkey.py (new), tests/test_1110_jobsfeed.py (new). No change to requirements.txt (apify >= 4.1, < 4.2), the Dockerfile, the dataset or output schema, or prices.
Unreleased: state store errors and no empty dataset (GAP16)
A state store that cannot be opened (an invalid stateStoreName such as Bad Name!!, a store owned by another account, limited permissions) used to crash the run with a traceback (exit 91) and an empty dataset when onlyNewJobs, includeExpired or trackFirstSeen was on. Now it logs a warning and the run goes on as a first run with nothing saved; RUN_SUMMARY gets stateStoreUnavailable: true and the status message says so (same as the rss, sitemap and remote Actors).
When no board could be read and nothing was written (for example robots.txt could not be fetched), the run now also pushes one free status item (no charged event), so the dataset is never empty. The exit status is unchanged: the run still fails when every entry failed.
GAP16 changed these files: CHANGELOG.md, my_actor/main.py, tests/test_gap16_store_and_empty_dataset.py, tests/test_gap8_demo.py (test_broken_user_board_still_fails_loudly now expects the free status row). No change to .actor/input_schema.json or .actor/actor.json.
Input form prefill:companies is prefilled with the demo board (https://boards.greenhouse.io/airbnb ) and maxTotalJobs with 4, so a Store visitor sees a real example instead of an empty form. No schema default was added: companies still has no default and maxTotalJobs still defaults to 0, so an API run with {} is unchanged (the GAP8 demo).
The prefilled input runs as the demo: new is_sample_input() in my_actor/main.py. When companies is exactly the demo board (a trailing / is ignored) and maxTotalJobs or maxJobsPerCompany is between 1 and 4, the run takes the demo path (demo_input(), the demo cap and time limit, RUN_SUMMARY.demoMode). The log says Demo mode: prefilled sample input, returning up to 4 sample jobs from https://boards.greenhouse.io/airbnb and the status message starts Demo mode (prefilled sample input): . So the Store test input costs what {} costs: at most 4 × $0.002 = $0.008. Any other board, a second entry, or a cap of 0 or above 4 is a normal run, exactly as before.
exampleRunInput in .actor/actor.json was {"maxTotalJobs": 4}; it is now the same as the prefill (the GAP12 test requires that).
Schema descriptions of companies and maxTotalJobs mention the prefill and its cost.
README: new "What you get" section near the top, "Input examples" (three inputs, each run locally on November 1, 2026) with a real output item from the prefilled input, a sample-run pricing line, and an FAQ entry on which dataset rows are free. The demo paragraph and input table mention the prefill.
Tests: tests/test_gap8_demo.py now expects the companies prefill to be the demo board (it used to require no prefill; the no-default assertion stays). New tests/test_gap15_sample_input.py covers the prefill, the sample input taking the demo path, {} being unchanged, and other inputs being normal runs.
Docs: the README demo paragraph said the demo stops after 60 seconds; the cut-off has been 50 s since GAP12 (DEMO_TIMEOUT_SECS = 50).
Review fixes (GAP15b, README and this changelog only, plus the heading check in tests/test_gap15_sample_input.py): "What you get" is renamed "At a glance" and its first bullet names the platform; the FAQ says the status row is written when the demo or a time-limited run "ends without any job row" (the code condition is (demo or cut) and not runner.pushed, so it also covers a demo whose filters removed every job) and says to keep rows without status, or with status: "active", to get only jobs.
GAP15 changed these files: .actor/actor.json, .actor/input_schema.json, CHANGELOG.md, README.md, my_actor/main.py, tests/test_gap15_sample_input.py, tests/test_gap8_demo.py. The .actor/actor.json version is unchanged.
Unreleased: changelog file lists and version 1.0 (GAP13)
.actor/actor.json version is now 1.0 (was 1.1), the version that exists on the Apify platform. New builds are numbered 1.0.x. No code or input change.
GAP13 changed these files: .actor/actor.json, CHANGELOG.md. No change to .actor/input_schema.json.
GAP12 changed these files: .actor/actor.json, CHANGELOG.md, README.md, my_actor/main.py, my_actor/runguard.py, my_actor/sources.py, tests/test_gap12_example_input.py, tests/test_gap12_runguard.py, tests/test_gap8_demo.py. In .actor/actor.json GAP12 only added exampleRunInput (shown in the GAP12 entry below); it did not change the description, the version or any other field. GAP12 made no change to .actor/input_schema.json (defaults, prefill and field texts are as before).
Unreleased: fail soft and a time budget for the Store test (GAP12)
Fail soft in the demo: when the sample board cannot be read, the demo no longer fails the run. It pushes one free status item (no charged event) with the reason, logs a warning, and ends SUCCEEDED. A run cut short by the time budget with no job does the same. A run on your own boards where every board fails still fails, as before.
The demo is now cut off after 50 s (was 60 s).
Time budget: the demo run ({}, the prefill or the exampleRunInput) starts no new request after about 40 s, uses a 10 s timeout per request with at most 2 attempts and waits at most 2 s between them (a long Retry-After is capped). Every run, demo or not, also stops starting requests 20 s before the platform timeout (ACTOR_TIMEOUT_AT) and gets cut off at most 10 s after that, so a slow or hung source can no longer make the run time out. When the platform aborts the run, no new request is started.
robots.txt is now fetched with one lock per host instead of one lock for all hosts, so one slow host no longer holds up the others.
New exampleRunInput in actor.json: {"maxTotalJobs": 4}. It matches the prefill and runs the same small demo.
Tests added for a source that is down, slow or hung, a partial failure, the time budget, the free status item and an unreadable state store.
Unreleased: a board listed twice is read and charged once; clean location strings (GAP11)
BREAKING (fewer charged records): the same board listed more than once in companies used to be read and charged once per entry (for example airbnb plus https://boards.greenhouse.io/airbnb gave every job twice and two charges per job). Entries are now matched on a normalized board key before anything is read: a slug or URL that differs only in letter case (Greenhouse, Ashby and the host-name vendors Recruitee, Personio, HireHive, Teamtailor and Workday), a trailing slash, a query string or vendor: prefix names one board on every vendor, including Polymer and HireHive. Lever keeps letter case (its board names are case-sensitive). The board is read once, by the first entry; later entries are skipped with a log line, nothing is read or charged for them, and they are listed in RUN_SUMMARY as duplicateEntries (input, sameBoardAs).
A Greenhouse, Lever or Ashby job ID read through two different entries is output and charged once (those IDs are unique across boards). On other vendors an ID is only unique per board, so jobs from different boards are never merged by ID. A job already output in this run is dropped before the push, so it is never charged; RUN_SUMMARY gets duplicateJobsDropped and the board duplicateJobs, only when that happened.
BREAKING (output values):location, every locations entry and country are trimmed and runs of whitespace (tabs, line breaks, non-breaking spaces) collapsed to one space, for every ATS; a space before a comma is dropped (Austin , TX becomes Austin, TX). United States is now United States, and locations no longer lists a value twice because of whitespace. An empty location becomes null.
The locations filter ignores extra whitespace in both the input term and the job's location, so United States matches United States.
Unchanged: uid, the onlyNewJobs state and inputs that list each board once.
New vendor: HireHive job boards, read through HireHive's official public Jobs API (https://<company>.hirehive.com/api/v2/jobs, no key or login). Used only when an entry is a <company>.hirehive.com URL or hirehive:<company>. Bare slugs, company names and the directory never probe HireHive, so existing inputs make the same requests as before.
BREAKING only when opted in: records from HireHive boards carry the new value hirehive in the existing ats field. No field is added or removed and no default changes.
The list endpoint includes descriptions, so there are no per-job detail requests. An unknown company (404) is reported as an unresolved entry. robots.txt on company hosts has no rules (checked 2026-10-29) and is still read and obeyed on every run.
Unreleased: Polymer boards (GAP9_POLYMER, opt-in)
New vendor: Polymer job boards, read through Polymer's official unauthenticated Public API for job board integrations (developer.polymer.co). Used only when an entry is a jobs.polymer.co/<company> URL, an api.polymer.co/v1/hire/organizations/<company> URL or polymer:<company>. Bare slugs, company names and the directory never probe Polymer, so existing inputs make the same requests as before.
BREAKING only when opted in: records from Polymer boards carry the new value polymer in the existing ats field. No field is added or removed and no default changes.
includeDescription on costs one extra request per Polymer job (the detail endpoint carries the description). An unknown organization (Polymer answers 422) is reported as an unresolved entry. Polymer's robots.txt on api.polymer.co is empty (checked 2026-10-29) and is still read and obeyed on every run.
Unreleased: Workday pathless rows and partial reads (GAP8, Ranger's review)
BREAKING (output): Workday list rows with no externalPath (no job page) used to be output with the bare site URL as url, deduped by title (so different jobs with the same title merged into one) and charged as jobs. They are now skipped: never pushed and never charged. The board's RUN_SUMMARY entry gets pathlessSkipped (distinct rows skipped), only when there were any, and the log says so.
BREAKING (RUN_SUMMARY): a Workday site whose jobs could not all be reached past the 2,000-row cap now has status: "partial" with a partialReason, instead of ok. This now also covers sites where no facet covers every job (for example only a distance facet is left): the best facet is still used, but the read is reported as partial and the log warns, where before it could log that facet splitting reached every job. As in GAP1, such a read never reports jobs as expired. boardsOk and the final status message count partial boards as read. A stop by maxJobsPerCompany or maxTotalJobs is not partial.
Unreleased: demo mode for an empty input (GAP8)
Behaviour change: an input with no companies (and no directory search), including {}, used to fail at the start. It now succeeds as a demo run: up to 4 sample jobs from https://boards.greenhouse.io/airbnb , charged at the normal per-job price (at most 4 job events), stopped after 60 seconds at the latest. The log line and status message start with Demo mode. RUN_SUMMARY gets demoMode and demoBoard only in demo runs.
Input schema: companies has no prefill and is not required, so Apify's Store test (which runs the prefilled default input) and an empty API call both run the demo. Inputs that list companies behave as before.
Unreleased: release fixes (input validation, docs, consolidated field list)
BREAKING (additive output fields), full list of fields added since the last release:
With includeExpired: status on every job record (active), plus free expired records with uid, id, title, url, companyName, lastSeenAt, expiredDetectedAt (GAP1).
With dedupeBy: companyTitle: locations (union), duplicateCount, mergedUids on merged records (GAP3).
With visaSponsorship other than any: visaSponsorship, visaSponsorshipEvidence; with maxYearsExperience: yearsExperienceMin, yearsExperienceMax (GAP5).
RUN_SUMMARY, only while the matching option is on: expiredRecords, agencyJobsExcluded, duplicatesDropped, salaryJobsExcluded, jobFiltersExcluded.
Input validation: negative numbers, a fractional count, minAnnualSalaryUsd above maxAnnualSalaryUsd and unknown option values (for example dedupeBy, timeRange) now stop the run at the start with one status message listing every problem (Actor.fail, no traceback). Nothing is fetched or charged. 0 and empty keep their existing meaning (off / no limit), and {} plus every previously valid input behave as before.
Behaviour change: an API or scheduled input with a negative limit (for example maxJobsPerCompany: -1) used to run and now fails at the start with a status message. A missing or too long companies list (none given and no directory search, or more than 2000) now also ends with a clean failed-run status message instead of a traceback; the run still fails as before. salaryCurrency is not an input of this Actor and is ignored, as before.
Docs: README and sample output show the new fields; the README states that USD conversion uses fixed approximate rates set in October 2026 (RATES_AS_OF), that isAgency, visaSponsorship and yearsExperienceMin/Max are heuristics, and that the visa and years filters are off by default and fetch job details, so they slow runs down.
New inputs, all off by default, ported unchanged from career-site-jobs-feed (same patterns, same values): seniority, employmentTypes, workArrangement, visaSponsorship (any / yes / not_no; default any = off), maxYearsExperience and timeRange (1h / 24h / 7d / 30d / all). timeRange, when set, replaces postedWithinDays; undated jobs still follow includeUndatedJobs. Dropped jobs are never pushed or charged. RUN_SUMMARY gets jobFiltersExcluded and each board filterExcluded, only while one of these filters is on.
BREAKING only when opted in (additive output fields):visaSponsorship + visaSponsorshipEvidence (with visaSponsorship other than any; the evidence snippet has e-mail addresses and phone numbers removed) and yearsExperienceMin + yearsExperienceMax (with maxYearsExperience) are added to every record while that filter is on. No existing field changes.
With visaSponsorship or maxYearsExperience on, job details are fetched even when includeDescription is off (more requests, slower runs); the description is still only output when includeDescription is on. A salary stated only in the description can then also fill salaryMin/salaryMax.
While any of these filters is on, maxJobsPerCompany is not passed to the Workday adapter, so the cap counts jobs after the filters.
With every new input left empty, which jobs are output, the requests made, the output fields and the cost of {} are unchanged.
Unreleased: salary in US dollars and salary filters (hasSalary, minAnnualSalaryUsd, maxAnnualSalaryUsd, includeJobsWithoutSalary)
BREAKING (additive output fields): every job record now has salaryAnnualUsdMin / salaryAnnualUsdMax: the annual range converted to whole US dollars with a fixed rate table bundled with the Actor (my_actor/fx.py, RATES_AS_OF). The rates are rough reference values, not live or official rates; no rate is fetched at run time. Null when there is no salary, no pay period, or the currency is not in the table (very-high-inflation currencies are left out on purpose). Consumers that reject unknown fields need updating; no existing field changes.
New inputs, all off by default: hasSalary keeps only jobs that state a salary; minAnnualSalaryUsd / maxAnnualSalaryUsd keep jobs whose annual USD range reaches the minimum and starts at or below the maximum; includeJobsWithoutSalary also keeps, under a USD bound, jobs whose salary is missing or cannot be converted. Dropped jobs are never pushed or charged. RUN_SUMMARY gets salaryJobsExcluded and each board salaryExcluded, only while a salary filter is on. On Workday, maxJobsPerCompany is no longer passed to the adapter while a salary filter is on, so the cap counts jobs after the filter.
With the filters off, which jobs are output, the state store and the cost of {} are unchanged.
Unreleased: duplicate removal (dedupeBy, opt-in)
New input dedupeBy (default none). job drops a job whose company, title and first location (the dedupeKey recipe) were already output in this run; the first one read wins. companyTitle merges the jobs of one company with the same title into one record: locations is the union of their locations, plus the new fields duplicateCount (jobs merged in) and mergedUids. Merged records are output when their board has been read; a later board of the run with the same company and title is dropped.
Duplicates are dropped or merged before the dataset push, so they are never charged; the only charged push is one per output record. RUN_SUMMARY gets duplicatesDropped and each board duplicates, only while the option is on.
BREAKING only when opted in (additive output fields): with companyTitle, records carry duplicateCount and mergedUids and locations can list more than one job's locations. With none (the default) output, state and the cost of {} are unchanged.
With onlyNewJobs, dropped and merged jobs are remembered as output. With includeExpired, a merged record is reported expired only when none of its members is listed. On Workday, maxJobsPerCompany is no longer passed to the adapter while dedupe is on, so the cap counts records after duplicates are removed.
Limits: only duplicates within one run are handled (a duplicate of a job output by an earlier run is output again unless onlyNewJobs is on). In companyTitle mode maxJobsPerCompany counts merged records.
Unreleased: recruiting-agency flag and filter (isAgency, excludeAgencies)
BREAKING (additive output field): every job record now has isAgency (true / false). It is true when the company name looks like a staffing or recruitment agency (generic words such as Staffing, Recruitment, Executive Search, Personalberatung, Zeitarbeit, or a short list of known agencies such as Randstad, Adecco, Hays, Robert Half, TEKsystems) or the description says the job is filled for a client ("on behalf of our client", "our client, a …", "für unseren Kunden … suchen wir", "im Auftrag unseres Mandanten", "pour le compte de notre client", "voor onze opdrachtgever"). Consumers that reject unknown fields need updating; nothing else in the record changes.
New input excludeAgencies (default false) leaves those jobs out. They are dropped before the dataset push, so they are never charged. RUN_SUMMARY gets agencyJobsExcluded and each board agencyExcluded, only while the option is on.
It is a heuristic (module my_actor/agency.py): an in-house job at an agency's own office is also flagged, and an agency with a neutral name and no client wording is not.
With includeDescription off only the company name is checked (Workday always reads the description). On Workday, maxJobsPerCompany is no longer passed to the adapter while excludeAgencies is on, so the cap counts jobs after the filter.
With excludeAgencies off, which jobs are output, the state store and the cost of {} are unchanged.
New input includeExpired (default false), ported from Career-Site Jobs Feed. On scheduled runs a free record with status: "expired" (uid, ats, companySlug, companyName, id, title, url, lastSeenAt, expiredDetectedAt, scrapedAt) is added for each job an earlier run returned that the board no longer lists. It is pushed without the job event, so it is never charged. New dataset view Expired jobs.
Only boards read completely are checked: a read cut short by maxJobsPerCompany, maxTotalJobs, the cost limit or an abort, or a Workday site with rows past the 2,000-row cap that facet splits could not reach, reports nothing as expired. Jobs that Workday title filters or onlyNewJobs drop before the detail request still count as listed.
State: a new <key>-live entry per board in the state store. When a job expires its seen and first-seen entries are dropped, so a job that comes back is returned as new.
With includeExpired on, job records get status: "active", and RUN_SUMMARY gets expiredRecords plus expired / complete per board. With it off (the default), output, state and cost are unchanged, so nothing here is breaking.
Unreleased: Greenhouse workplaceType and employmentType from the board's custom fields
Greenhouse has no standard workplace or employment field, but many companies publish them as custom job-board fields (the API's metadata), e.g. Airbnb Workplace Type (Remote, Hybrid), Instacart Employment Type and Time Type (Full time), Faire Employment Type (Regular, Intern, Temporary). These are now read: workplaceType/employmentType (normalized) and workplaceTypeRaw/employmentTypeRaw (the board's text) are filled, and isRemote is also true when the workplace field says Remote.
Field names read (case-insensitive): workplace type, workplace, location type, remote status, remote type, work arrangement, work location type, work model; employment type, job type, time type, worker type, employee type, employment status, position type, commitment. No other custom field is read.
Boards without such a field still give null, e.g. GitLab, whose only custom field is Quota Coverage Type (this is why run aUDW02fSc9lOwjyPJ had null for both).
Unreleased: Workday sites on myworkdaysite.com and embedded career sites
Workday URLs of the form https://wdN.myworkdaysite.com/[locale/]recruiting/<tenant>/<site> are now accepted. They are read through https://<tenant>.wdN.myworkdayjobs.com/<site>, the same career site and API, so the tenant's robots.txt there applies (myworkdaysite.com's own robots.txt has no rules) and job URLs in the output use the myworkdayjobs.com form.
A company careers page that embeds a Workday site (the page's window.workday config names the tenant, site and data center) is now recognized, as well as pages that link to a myworkdaysite.com URL.
Workday has no custom (vanity) domains for career sites, so nothing else changes.
Unreleased: no more placeholder Greenhouse requisition IDs
Greenhouse requisitionId is now null when the company's field holds a placeholder (ONE, MULTI, TBD, See Opening ID) or a free-text note instead of an ID. Only a single code of up to 40 characters that contains a non-zero digit (R-107348, REQ52463, SOPS_AMER_TBH#23986) is kept, trimmed. On 12 boards checked on 2026-10-28 this nulled 961 of 3,141 non-empty values, including every Stripe job and most Airbnb jobs.
Unreleased: one vocabulary for workplaceType and employmentType
Breaking for exact-value filters:workplaceType is now always remote, hybrid, onsite or null, and employmentType is always one of the schema.org values FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, INTERN, VOLUNTEER, PER_DIEM, OTHER, or null, whatever the ATS. Before, each ATS's own spelling was passed through (on-site, OnSite, Full-time, FullTime, Full time).
The ATS's own text is kept in the new fields workplaceTypeRaw and employmentTypeRaw.
A workplace value that says nothing clear (Workday's Flexible, Lever's unspecified) becomes null; an employment value that fits none of the types (Lever's Permanent) becomes OTHER.
Unreleased: robots.txt rule for every host
If a host's robots.txt can't be read (a server error, a page that isn't a robots file, or a network failure), the whole host is now skipped for the run with a warning in the log, on every ATS. Before, only Workday hosts were skipped and other hosts were read without rules.
A server error or network failure on robots.txt is retried once, 1.5 seconds later, before the host is skipped.
A missing robots.txt (any 4xx) still means no rules. A readable robots.txt is obeyed as before.
The rule also covers detection probes: company-name and slug auto-detection, board-name lookups and careers-page sniffing. A careers page that redirects to another host is now followed one hop at a time, and each host's robots.txt is checked before its page is fetched. A host skipped this way counts as no board, and the run carries on with the other hosts.
Unreleased: monitoring keeps jobs that are still listed
Jobs that stay listed for more than 120 days no longer come back as "new". With onlyNewJobs (or trackFirstSeen) on, every run now refreshes the last-seen time of each known job it finds, not only of jobs it outputs. A job is forgotten only after 120 days in which no run saw it.
Known Workday jobs cost no detail request. With onlyNewJobs on, jobs already in the state are dropped before their detail page is read, and they no longer count toward maxJobsPerCompany.
Unreleased: Workday sites with more than 2,000 jobs
Large Workday sites are read in full. Workday's job list never returns more than 2,000 rows for one query, so sites such as NVIDIA (about 2,700 jobs) were cut off at 2,000 without a warning. When a site reports 2,000 or more, the Actor now splits the query by the site's own category filters (for example job family or location) and merges the results, without duplicates.
If some jobs still can't be reached that way, the log says how many and which filter values are still capped.
Unreleased (2026-10-28): Workday fields no longer depend on includeDescription
Fixed
Workday detail pages are always read. Before, turning includeDescription off skipped them, so employmentType, country, requisitionId, hiringEntity and the extra locations came back empty. Now they are filled in either way, and includeDescription only decides whether the description is in the output. Turning it off no longer saves requests.
Workday companyName is filled in. It is the hiring entity without its leading company code (2100 NVIDIA USA becomes NVIDIA USA). It is null only when the detail page could not be read, and it is never the tenant slug. This replaces the earlier 1.0.x behavior (2026-10-28), where Workday companyName was always null.
Workday postedAt is a calendar date (2026-10-28, no time). Labels such as "Posted Today" are counted on the US Eastern calendar. Before, they were counted in UTC, so evening postings could show the next day. For "Posted 30+ Days Ago" the posting start date from the detail page is used.
Multi-location Workday jobs no longer show "3 Locations" as their location. The full list comes from the detail page.
Remote detection on Workday also looks at the primary location in the job URL, for example US-Remote.
Pay from the description and searchInDescription work on Workday with includeDescription off, because the description is always read.
postedWithinDays compares date-only values by calendar day.
Changed
Default run memory is now 1024 MB (was 512 MB).
Added tzdata to requirements.txt so the US Eastern calendar works in the container.
1.0.x (2026-10-28)
Changed: companyName value
companyName is now the company's real name as published by the board or its API (for example Ramp on Ashby, Palantir Technologies on Lever), or the name you typed when the board publishes none.
It is never the board slug any more. Before this change, boards without a published name returned the slug (ramp, nvidia).
Workday:companyName is now null. Workday job data names only the legal entity, which is in hiringEntity.
If you joined or grouped on companyName, use companySlug for a stable board key.
Company-name lookup:Stripe or Hugging Face is looked up in the directory, then up to four slug spellings are tried on each ATS (except Workday), at most two ATS endpoints at a time.
Unresolved records: an entry that cannot be resolved gives one record with status: "unresolved", input, reason, triedSlugs and triedAts. These records are not charged. RUN_SUMMARY counts them in unresolvedRecords.
New fields:workArrangement, seniority, salaryAnnualMin/salaryAnnualMax, postedAtPrecision, expiresAt, dedupeKey, firstSeenAt/lastSeenAt.
New inputs:trackFirstSeen (default false) and redactContacts (default true).
Fixed
robots.txt is requested with Accept: text/plain. Workday returned its HTML app shell to the old JSON Accept header, which was read as "no rules".
A robots.txt response that is HTML or not text/plain is now logged as unreadable, and Workday career sites on that host are skipped.
The Workday site path (/<site>/) is checked before any job data is read, so sites such as Pfizer's /InternalJobs/ are skipped.
Names with spaces are no longer read as domains. For example, Acme Robotics, Inc. was treated as a careers-page URL.
Unchanged
If every entry fails, the run still fails, listing the failed entries.
Pricing is unchanged: $0.002 per job written to the dataset, no start fee, and unresolved records are free.