Instahyre Jobs Search Scraper

This local-only Apify Actor extracts public Instahyre job records through the existing official JSON API at https://www.instahyre.com/api/v1. Requests use ordinary direct access, one at a time, with no custom headers, proxy, fingerprinting, retries, or automatic redirects. The platform status is separate from dataset resultStatus. HTTP 401/403/429/451 or a visible source-authored denial/challenge stops the run as SUCCEEDED/SKIPPED and discards buffered rows; generic HTTP/transport failures are SUCCEEDED/DEFERRED when no complete rows exist, or SUCCEEDED/LIMITED when complete rows were retained. A fatal error with no stored complete row is FAILED/FAILED; a clean empty search is SUCCEEDED/NO_DATA. Receipts and diagnostics stay in key-value storage and are never emitted as dataset rows. No Cloud calls or publishing are performed.

Modes

• search: bounded public API search with optional location, remote, internship, and experience filters.
• searchMultiple: runs up to three independent public API queries.
• single: fetches one verified public job URL.
• multiple: fetches up to ten verified public job URLs.

Every job record is enriched through the existing employer_public_jobs/{id} endpoint and admitted to the dataset only after title, company, location, description, ID, public URL, detail identity, and the 21-meaningful-source-fact threshold pass. A later non-barrier failure does not erase already verified rows. Unavailable optional values are omitted; employment type is never inferred from a non-internship flag, and no application URL is fabricated because the public API does not expose one.

Local commands

npm install --ignore-scripts --no-package-lock
npm test
npm run lint
apify validate-schema .actor/input_schema.json
$env:APIFY_LOCAL_STORAGE_DIR = ".\storage-instahyre-local-validation"
if (Test-Path $env:APIFY_LOCAL_STORAGE_DIR) { throw "Choose a new, nonexistent actor-relative storage directory before running." }
apify run --resurrect --input-file INPUT.json
npm run validate

Use INPUT-single.json, INPUT-multiple.json, or INPUT-search-multiple.json to exercise the other modes. Before each local run, select a fresh relative storage directory and confirm it does not exist; never use --purge or reuse a dataset directory. The validator reads that same APIFY_LOCAL_STORAGE_DIR, reconciles the actual dataset with OUTPUT, OUTPUT_SUMMARY, and REQUEST_RECEIPTS, and rejects sparse, duplicate, unverified, or sub-threshold records. No dataset files should be edited by hand.

Output highlights

Records include the source API payloads, canonical public URL, readable description and sections, company facts and source-published links, locations, remote status, experience range, skills, job functions, category, recruiter details, explicitly supplied employment/internship flags, sectioned responsibilities and qualifications, structured job-posting data, request receipts, field coverage, and data-quality flags. Each emitted record has at least 21 distinct meaningful source facts; salary, date, review, industry, and other values are included only if the public API response actually provides them.