Drushim.co.il Scraper — Israel Job Listings

Drushim.co.il Scraper — Israel Job Listings

This actor collects job listings from Drushim.co.il, one of Israel's largest job boards (operated by the Yad2 group). It calls Drushim's internal JSON search API directly and extracts every entry returned in ResultList — no browser, no HTML parsing, no job-detail-page requests. RecommendedJobs entries are not collected, so every delivered record is a real, searched-for listing. Use it for recruiter lead lists, market/salary-band research (Israel hi-tech and general labor market), competitor hiring intelligence, or feeding job data into your own job board or ATS integration.

Features

• Full-text + faceted search against Drushim's live index (keyword search today; category/region/ employment-type/experience filters are supported by the underlying API for future input expansion).
• 54 structured fields per listing — identity, employer, dates, geo (region/zone/city/lat-lon), classification (category/sub-category), experience level, employment type/arrangement, listing flags (sponsored/hot/top/expired), full description in three formats (HTML/plain/Markdown), and a content hash for change detection.
• $0-COGS official/internal-API access — no residential proxy fragility, no anti-bot arms race; the actor talks to the same JSON endpoint the Drushim.co.il website itself uses.
• Pay only for delivered listings — every chargeable event is a validated, deduplicated job record.

How to use

1. Open the actor and enter a searchTerm (defaults to developer so a first run works with zero configuration).
2. Set maxResults (how many listings to deliver) and pagesToFetch (how many result pages to pull).
3. Click Start. Default input returns results in well under a minute.
4. Export the dataset as JSON/CSV/Excel, or pull it via the Apify API/SDK.

Pricing

This actor uses pay-per-event billing. Each delivered job-listing event costs USD 0.0013 — a launch undercut of the category comparator's live per-record price ($0.00149/record, i.e. $1.49/1k), computed via the fleet's Pricing Engine v2 (cheapest-anchor mode, 0 reviews, quality parity 1.0). Scraping 1,000 job listings costs approximately $1.30.

Input & Output example

Input:

{
  "searchTerm": "developer",
  "maxResults": 50,
  "pagesToFetch": 1
}

Output (one item, abridged):

{
  "jobId": 37572693,
  "title": "QA Automation Engineer",
  "company": "QuaityAI",
  "url": "https://www.drushim.co.il/job/37572693/0b47173a/",
  "applyUrl": "https://www.drushim.co.il/sendcv.aspx?jobcode=37572693",
  "primaryCity": "כרמיאל",
  "primaryCityEn": "Karmiel",
  "zone": "North",
  "employmentType": "משרה מלאה",
  "experience": "1-2 שנים",
  "categories": ["הייטק-תוכנה", "הייטק-QA"],
  "isRemote": false,
  "isHybrid": false,
  "datePosted": "2026-06-30",
  "description": "...",
  "source": "drushim.co.il",
  "scrapedAt": "2026-07-18T03:41:44.802818+00:00"
}

Full field groups:

• Identity and application: Job ID, title, listing URL, application URL, external-application indicator, and employer job code.
• Employer: Company name, company code, company URL, logo URL, and confidential-employer flag.
• Dates: datePosted reflects the listing's current or bumped date when supplied by Drushim. dateActual and firstPublishedDate preserve the original publication timing. postingAge represents the available posting-age value.
• Location: Region and region codes, zones, Hebrew zone names, cities, primary city names, and latitude/longitude where available.
• Classification: Categories, category codes, subcategories, and subcategory codes.
• Experience: Experience description and code, plus the allowNoCv indicator.
• Employment and work arrangement: Employment type and codes, isRemote, and isHybrid.
• Listing flags: Hitech, sponsored, top-job, hot-job, expired, and classified-job indicators.
• Description: HTML, plain-text, and Markdown descriptions, together with requirements when provided.
• Compensation: salaryRange, salaryMin, salaryMax, salaryRaw, and currency. Salary fields are always null — Drushim listings do not publish salary data (true for every actor reading this source, not a limitation of this scraper).
• Source metadata: source, scrapedAt, and contentHash. The hash identifies the collected listing content and can help detect changes.

Inputs

• searchTerm: Search keyword or phrase submitted to Drushim.co.il.
• maxResults: Maximum number of job listings to deliver.
• pagesToFetch: Number of JSON search-result pages to request.
• proxyConfiguration: Proxy settings for API requests. The default proxy group is RESIDENTIAL; the configuration intentionally does not pin requests to a country.

FAQ / Disclaimer

• Does this include salary data? No — Drushim.co.il does not publish salary figures on listings, so the salary fields are always present in the schema but empty. This matches the source data, not a gap in extraction.
• Is this affiliated with Drushim.co.il? No. This is an independent data-collection tool built against Drushim's public search API; it is not endorsed by or affiliated with Drushim.co.il or the Yad2 group.
• Support: open an Issue on the actor's Apify Store page for bugs or field requests.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.