Foundit Jobs Search Scraper

Extract current public job postings from Foundit's first-party search and detail APIs. The actor saves only records whose detail response matches the search result and contains a readable public description.

Input

Field	Default	Description
keyword	developer	Non-empty role, title, or skill query.
maxItems	20	Maximum complete detail-verified records, from 1 to 500.
maxPages	20	Search-page safety cap, from 1 to 100.

{
  "keyword": "developer",
  "maxItems": 20,
  "maxPages": 20
}

Output

Each dataset record contains the public Foundit job and employer facts exposed by the search/detail responses: title, company, locations, experience, employment, published salary, structured skills and synonyms, classifications, sectioned description text and HTML, responsibilities, requirements, benefits, education, dates, public application/detail URL, publishing flags, identifiers, related-content counts, and direct request provenance. Records normally contain well over 20 populated meaningful fields; source fields that Foundit does not publish are omitted.

The actor writes OUTPUT_SUMMARY, REQUEST_RECEIPTS, RUN_DIAGNOSTICS, OUTPUT, and RUN_HEALTH to the default key-value store. Dataset records never include raw API payloads, recruiter metadata, or contact details; contact-like data in a public description is redacted.

Access policy

Requests use ordinary direct HTTPS with fixed timeouts, no proxy, no stealth or fingerprint changes, no alternate identity, and no retries. An explicit HTTP 401/403/429/451 response or human-verification/access-denial challenge stops the run and marks the result SKIPPED, discarding buffered rows. HTTP 407 or another unverified transport/source response is DEFERRED, not a block; already verified buffered rows are retained.

Run lifecycle

OUTPUT.status is the Apify platform status (SUCCEEDED or FAILED); OUTPUT.resultStatus is the extraction outcome (COMPLETE, LIMITED, SKIPPED, NO_DATA, DEFERRED, or FAILED). Only complete, detail-verified Foundit job records enter the dataset. Diagnostics and request receipts are stored in KVS. A later error after dataset writes preserves those rows and finishes SUCCEEDED/LIMITED; a fatal zero-row run finishes FAILED. NO_DATA requires a successful direct first-party search receipt, an empty result array, and an explicit numeric zero total for the requested keyword; unrecognized empty responses remain DEFERRED.

Use the actor only for public, source-grounded job data and respect Foundit's terms and applicable law.