Flexjobs Jobs Search Scraper

This Actor searches the public FlexJobs job API and sequentially verifies each selected public detail API response before emitting a record. It uses ordinary direct HTTPS only: no proxy, stealth, fingerprint change, alternate identity, retry control, or raw API payload output.

Input

The public input contains only query, maxItems, and maxPages. Fixture, context, raw-payload, timeout, retry, proxy, and user-agent controls are intentionally absent.

Dataset

Records preserve public FlexJobs metadata such as title, description and summary, remote-work/location coverage, schedules, employment types, career levels, travel, compensation when published, education, benefits, categories, employer accolades, dates, application status, public flags, identifiers, ranking score, public listing/detail URLs, API receipts, and quality/provenance evidence. Contact data and raw API payloads are omitted.

FlexJobs’ public detail UI visibly gates additional employer and job content behind its subscription lock. The Actor records this limitation and does not invent company or application fields when the public API does not publish them.

Records are buffered until matching detail data is verified. Only complete job records are pushed to the dataset; partial records and run diagnostics are not dataset rows. A complete record must contain a readable public description and more than 20 meaningful source-grounded fields.

Access policy

HTTP 401, 403, 429, 451, or an explicit CAPTCHA/human-verification/access-denied response stops the API route and writes SKIPPED evidence without publishing records. HTTP 407, redirects, invalid JSON, and unverified transport failures are recorded as DEFERRED. The Actor never attempts to bypass a site barrier.

Run lifecycle and evidence

The OUTPUT key keeps Apify platform status (SUCCEEDED or FAILED) separate from extraction resultStatus (COMPLETE, LIMITED, SKIPPED, NO_DATA, DEFERRED, or FAILED). NO_DATA is used only when the successful first-party search response has an empty result array and explicitly reports totalCount: 0 for the requested query; ambiguous empty responses remain DEFERRED. A confirmed access barrier discards all buffered records; an unverified transport failure is DEFERRED, not a block. If an error occurs after dataset rows have been stored, those rows are retained and the run finishes SUCCEEDED with resultStatus: LIMITED. A fatal error before any row is stored finishes FAILED. Request receipts, diagnostics, the detailed summary, and health state are written to KVS keys REQUEST_RECEIPTS, RUN_DIAGNOSTICS, OUTPUT_SUMMARY, and RUN_HEALTH.

Local validation

npm install --ignore-scripts --no-audit --no-fund
npm test
npm run check
apify validate-schema
apify run --purge --input-file ./INPUT.json
npm run validate:dataset -- storage --require-data