Jora Jobs Search Scraper

What does Jora Jobs Search Scraper do?

This Apify Actor extracts complete, publicly available job postings from Jora. It uses native HTTPS and Cheerio with optional Apify Proxy routing. A row is emitted only after the public Jora detail URL, posting ID, employer, location, description, and query relevance have been verified.

Why use Jora Jobs Search Scraper?

• Search supported Jora country sites with bounded pagination and detail concurrency.
• Collect full detail descriptions rather than abbreviated listing cards.
• Verify canonical URLs, 32-character IDs, employer/title consistency, and query relevance.
• Schedule runs, call the Actor API, export datasets, and connect Apify integrations.
• Enable proxy routing only when public detail access requires it.

How to scrape Jora jobs

1. Open the input tab and select a mode.
2. Choose a country, query, and optional location.
3. Start with one page and a low maxItems limit.
4. Enable Apify Proxy only when direct requests are blocked.
5. Run the Actor and inspect both the dataset and structured diagnostics.
6. Download results or connect them through the Apify API.

Modes

• search: search one query, then enrich bounded result cards from public Jora detail pages.
• searchMultiple: run up to five queries and deduplicate verified records.
• single: fetch one official Jora detail URL.
• multiple: fetch up to ten official Jora detail URLs.
• startUrls: accept a bounded mixture of official search and detail URLs.

Input

Field	Type	Default	Description
mode	string	search	search, searchMultiple, single, multiple, or startUrls.
query	string	developer	Search phrase for search.
queries	string[]	[query]	Up to five phrases for searchMultiple.
location	string	—	City, state, or region.
country	string	au	Supported Jora country subdomain, such as au, nz, ca, sg, or uk.
url	string	—	Official detail URL for single.
urls	object[]	—	Objects containing official detail URLs for multiple.
searchUrls	string[]	—	Official search URLs for bounded search runs.
startUrls	object[]	—	Objects containing official search or detail URLs for startUrls.
maxItems	integer	3	Maximum records per query/direct mode; 1–10.
maxPages	integer	2	Maximum search pages; 1–3.
concurrency	integer	4	Maximum concurrent detail requests; 1–5.
requestTimeoutSecs	integer	25	Per-request timeout; 5–45 seconds.

Example:

{
  "mode": "search",
  "query": "developer",
  "location": "Sydney",
  "country": "au",
  "maxItems": 3,
  "maxPages": 2,
  "concurrency": 4,
  "requestTimeoutSecs": 25
}

What data can Jora Jobs Search Scraper extract?

Field	Type	Description
jobId	string	Verified Jora posting identifier
jobTitle	string	Public job title
employer	string	Hiring organization
location	string	Published job location
workArrangement	string	Remote, hybrid, or on-site signal
description	string	Complete normalized detail description
salary	string	Published compensation when available
publicUrl	string	Canonical Jora posting URL
applicationUrl	string	Explicit application link when published

How much will it cost to scrape Jora?

The Actor uses lightweight HTTP requests, so compute usage is normally modest. Cost depends on run duration, memory, limits, and optional proxy traffic. Start with one page and a few jobs to estimate account-specific cost. Proxy use is disabled by default.

Output and run state

Job rows contain stable IDs, canonical/public URLs, title, employer, location, address, salary fields, employment type, work arrangement, categories/tags, listing highlights, dates, readable description and HTML, description sections, responsibilities/qualifications/benefits when published, explicit application links only, search provenance, verification receipts, retrieval metadata, and quality counts.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. RUN_SUMMARY, RUN_DIAGNOSTICS, RUN_SKIPS, and RUN_HEALTH are stored in the default key-value store. Access-denied or anti-bot responses fail closed and never become fabricated job rows.

The Actor does not use fingerprint generation or challenge bypass. Run metadata records whether direct transport or Apify Proxy was used.

Local verification

From this directory:

npm install --ignore-scripts --no-audit --no-fund
npm test
npm run lint
npx --yes apify-cli validate-schema .actor\input_schema.json
npx --yes apify-cli run --purge --input-file INPUT.json
npm run validate

The checked-in INPUT.json is the reproducible primary search input. Storage is written below storage/ and is intentionally local.

FAQ, disclaimer, and support

Why is a run BLOCKED?

Jora search pages may load while detail pages return an access block. Review RUN_DIAGNOSTICS and try a small proxy-enabled run when appropriate.

Does the Actor collect candidate data?

No. It collects public job advertisements only and does not access authenticated candidate or employer systems.

Our Actors are ethical and do not extract private user data. Results can still contain personal data published in an advertisement. Personal data is protected by the GDPR and other regulations. Do not process it without a legitimate reason; consult your lawyers if unsure. Use the API tab for programmatic access and the Issues tab for support.

Responsible use

Collect only public job information, respect Jora’s terms and robots directives, and follow applicable privacy and data-protection requirements. Do not use the Actor for authenticated pages, paywall circumvention, or candidate personal-data harvesting.