JobMaster Israel Jobs Scraper avatar

JobMaster Israel Jobs Scraper

Pricing

from $2.99 / 1,000 jobmaster job records

Go to Apify Store
JobMaster Israel Jobs Scraper

JobMaster Israel Jobs Scraper

Monitor public JobMaster.co.il listings by Hebrew or English keyword with title, company, city, job type, short description and direct URL.

Pricing

from $2.99 / 1,000 jobmaster job records

Rating

0.0

(0)

Developer

Jobs API

Jobs API

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

21 days ago

Last modified

Categories

Features

Limited permissions

Share

JobMaster.co.il - Israel Jobs

CSV rank: 1355. Store listing: swerve/jobmaster-scraper.

This Actor monitors public JobMaster.co.il search results by Hebrew or English keyword. It follows the public checknum.asp?key=... links and returns only complete current jobs with jobId, direct url, title, company, city/location, job type, an 80+ character public description, the search keyword, and source provenance.

JobMaster exposes about ten fresh anonymous results per keyword. Supply multiple keywords to widen monitoring coverage; records are de-duplicated by job ID. The implementation uses sequential direct public requests without a proxy or custom headers. Explicit access boundaries stop the run, discard buffered jobs, and retain status and request receipts in the key-value store; sparse candidates and empty result sets are diagnostics, never dataset rows.

Example:

{
"keywords": ["מפתח", "QA", "software"],
"maxItems": 20,
"requestTimeoutSeconds": 45
}

Local verification:

apify validate-schema
npm run lint
npm test

Before a local Actor run, preserve existing apify_storage, confirm a new relative APIFY_LOCAL_STORAGE_DIR does not exist, and use --resurrect without --purge per the root AGENTS.md instructions.

OUTPUT_SUMMARY.status reports the Apify run lifecycle (SUCCEEDED or FAILED); resultStatus separately reports COMPLETE, LIMITED, SKIPPED, DEFERRED, NO_DATA, or FAILED. successfulItems counts only dataset writes that resolved successfully. A confirmed source barrier discards buffered jobs and is SUCCEEDED/SKIPPED; generic HTTP, response-body, and transport unavailability is SUCCEEDED/DEFERRED when no records were stored. A later non-block failure or deferral preserves the stored prefix as SUCCEEDED/LIMITED. A fatal zero-row parser/runtime/write failure persists its summary and diagnostics best-effort before calling the SDK failure lifecycle.

Cloud deployment and bounded validation:

apify push
apify call jobsapi/jobmaster-jobs-search-scraper --memory 512 --timeout 300 --input-file .actor/input.json