# Changelog of Scrape Lever Jobs: Any jobs.lever.co Job Board (`fecklesspleb/lever-jobs-scraper`) Actor

- **URL**: https://apify.com/fecklesspleb/lever-jobs-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/fecklesspleb/lever-jobs-scraper.md

## Changelog

### Unreleased: prefilled sample input, README examples (GAP15)

- **Input form prefill:** `companies` is prefilled with the demo board (https://jobs.lever.co/spotify) and `maxTotalJobs` with 5, 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 5, 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 5 sample jobs from https://jobs.lever.co/spotify` and the status message starts `Demo mode (prefilled sample input): `. So the Store test input costs what `{}` costs: at most 5 × $0.001 = $0.005. Any other board, a second entry, or a cap of 0 or above 5 is a normal run, exactly as before.
- `.actor/actor.json` gets an `exampleRunInput` equal to the prefill (new test `tests/test_gap15_example_input.py`, copied from the Workday GAP12 test).
- 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.
- 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 now says an unreadable board is listed in `RUN_SUMMARY` as `error`, or `skipped` when robots.txt disallows it, and that the run fails only when every board fails with an error (all-skipped boards, or a demo that times out before its first job, end with an empty dataset).
- GAP15 changed these files: `.actor/actor.json`, `.actor/input_schema.json`, `CHANGELOG.md`, `README.md`, `my_actor/main.py`, `tests/test_gap15_example_input.py`, `tests/test_gap15_sample_input.py`, `tests/test_gap8_demo.py`. The `.actor/actor.json` version is unchanged.

### 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: `spotify`, `https://jobs.lever.co/spotify/` and `https://jobs.lever.co/spotify?lever-origin=applied` are one board. Lever board names are case-sensitive (`Spotify` is not found), so letter case is kept. 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 Lever job ID read through two different entries is output and charged once (Lever job IDs are unique across boards). 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.

### Unreleased: demo mode for an empty input (GAP8)

- Behaviour change: an input with no companies (and the directory off), including `{}`, used to fail at the start with "Add at least one careers board URL or company slug". It now succeeds as a demo run: up to 5 sample jobs from https://jobs.lever.co/spotify, charged at the normal per-job price (at most 5 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. Inputs that list companies behave as before.
- **BREAKING (Console form and Store test input):** the `companies` prefill (`palantir` and `https://jobs.lever.co/spotify`) is removed. The Console form now opens with no companies, so running it unchanged starts the demo (up to 5 sample jobs from https://jobs.lever.co/spotify) instead of reading the two prefilled boards. Saved tasks, schedules and API calls that list companies are not affected.

### Unreleased: shared Greenhouse source reads workplaceType and employmentType from board custom fields

- The shared ATS source code now reads Greenhouse custom job-board fields (the API's `metadata`) such as `Workplace Type` or `Employment Type` into `workplaceType`/`employmentType` (normalized) and `workplaceTypeRaw`/`employmentTypeRaw`. Only Greenhouse jobs are affected; output from this Actor's own ATS is unchanged.

### 2026-10-29: 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. Before, the 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 (for example Lever's `unspecified`) becomes null; an employment value that fits none of the types (for example Lever's `Permanent`) becomes `OTHER`.

### 2026-10-29: 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. Before, such a host was 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 lookups, careers-page sniffing). Redirects to another host are followed one hop at a time, and each host's robots.txt is checked first.
