Jora Jobs Scraper avatar

Jora Jobs Scraper

Pricing

Pay per usage

Go to Apify Store
Jora Jobs Scraper

Jora Jobs Scraper

A lightweight actor to scrape Jora jobs. Extracts job titles, companies, locations, and descriptions. For best results and to avoid blocks, use residential proxies. This fast and efficient scraper is perfect for reliable, up-to-date job data collection.

Pricing

Pay per usage

Rating

5.0

(5)

Developer

Shahid Irfan

Shahid Irfan

Maintained by Community

Actor stats

1

Bookmarked

115

Total users

37

Monthly active users

7.3 hours

Issues response

12 days ago

Last modified

Share

What does Jora Jobs Scraper do?

Jora Jobs Scraper collects public job listings from Jora and saves them as structured dataset records. Search by job keyword and location, select a supported Jora country site, or provide a direct Jora search URL. Results can include job titles, companies, locations, salaries, employment types, posting dates, descriptions, job URLs, and source metadata.

Use the dataset for hiring market research, salary analysis, recruitment research, job board aggregation, company hiring monitoring, or scheduled career intelligence workflows across Australia, Hong Kong, Indonesia, Malaysia, New Zealand, and Singapore.

Why use Jora Jobs Scraper?

  • Regional job coverage - Search six Jora country sites from one Actor input form.
  • Flexible search setup - Use a keyword and optional location, or start from a public Jora search URL.
  • Recent listing filters - Limit results to jobs posted within 24 hours, 7 days, or 30 days.
  • Useful job detail - Collect available salary, employment type, posting date, and description information alongside each listing.
  • Pagination controls - Set both the number of records and the maximum number of result pages to process.
  • Efficient result collection - Stops requesting additional pages after the requested result count is reached.
  • Structured output - Download JSON, CSV, Excel, or XML datasets for analysis, reporting, and automation.
  • Repeatable workflows - Run on demand, schedule recurring searches, use webhooks, or access results through the Apify API.

What data can you extract from Jora?

FieldTypeDescription
titleStringJob title shown in the listing.
companyStringHiring company when available.
locationStringJob location shown by Jora.
salaryStringSalary or compensation text when published.
job_typeStringEmployment type or related job classification when available.
date_postedStringPosting date or relative age shown by the listing.
description_textStringClean plain-text job description when available.
description_htmlStringSanitized HTML version of the description when available.
urlStringDirect Jora URL for the job listing.
sourceStringSource label for the listing, normally jora.
job_idStringJora job identifier when available.
sponsoredBooleanWhether Jora identifies the listing as sponsored.
countryStringCountry site selected for the run.
search_keywordStringKeyword used for the search.
search_locationString or nullLocation input used for the search.
search_pageInteger or nullResult page where the listing was found.

Optional values are omitted when Jora or the original listing does not publish them. This is expected for fields such as salary, job type, company, and descriptions.

How to scrape Jora jobs

  1. Open Jora Jobs Scraper in Apify Console.
  2. Enter a keyword such as software engineer and optionally add a city or region.
  3. Select the Jora country site, or enter a complete public Jora search URL in startUrl.
  4. Choose the posting-date filter, result limit, and page limit.
  5. Start the Actor and review the dataset preview.
  6. Download the results or connect the dataset to your research, reporting, or automation workflow.

When startUrl is provided, the Actor uses that URL as the search starting point. When it is empty, the Actor builds a search from keyword, location, and country.

Input Parameters

ParameterTypeRequiredDefaultDescription
startUrlStringNoEmptyPublic Jora search URL to use as the starting point.
keywordStringNosoftware engineerJob title, skill, or phrase to search for when startUrl is empty.
locationStringNoEmptyCity, region, or other location filter. Leave empty for a broader search.
countryStringNoAustraliaJora site to search: Australia, Hong Kong, Indonesia, Malaysia, New Zealand, or Singapore.
posted_dateStringNoanytimePosting-date filter: anytime, 24h, 7d, or 30d.
results_wantedIntegerNo20Maximum number of jobs to save, from 1 to 500.
max_pagesIntegerNo10Maximum number of search result pages to process, from 1 to 50.
proxyConfigurationObjectNoApify Proxy presetOptional Apify Proxy settings for runs that need proxy routing or additional reliability.

Output Data

Each dataset item represents one Jora job listing. Fields that are not available in the source listing may be omitted.

FieldTypeDescription
titleStringJob title.
companyStringCompany name when available.
locationStringListing location when available.
salaryStringSalary or compensation text when available.
job_typeStringEmployment type when available.
date_postedStringDate or relative posting age when available.
description_textStringPlain-text description when available.
description_htmlStringHTML description when available.
urlStringDirect Jora job URL.
sourceStringListing source label.
job_idStringJob identifier when available.
sponsoredBooleanSponsored-listing indicator when available.
countryStringSelected Jora country site.
search_keywordStringKeyword used in the run.
search_locationString or nullLocation used in the run.
search_pageInteger or nullSearch result page number.

Usage Examples

Collect up to 20 software engineering jobs in Sydney using the default Australia site.

{
"keyword": "software engineer",
"location": "Sydney",
"results_wanted": 20
}

Search Recent Jobs in Another Country

Collect data analyst roles posted during the last seven days on the Singapore Jora site.

{
"keyword": "data analyst",
"country": "Singapore",
"posted_date": "7d",
"results_wanted": 50,
"max_pages": 10
}

Use a Direct Jora Search URL

Start from a prepared Jora search page instead of building the search from separate keyword and location fields.

{
"startUrl": "https://au.jora.com/j?sp=search&q=software+engineer&l=Melbourne",
"results_wanted": 50,
"max_pages": 20
}

Sample Output

This example shows one dataset item. Optional fields may be absent when the listing does not publish the corresponding information.

{
"title": "Senior Software Engineer",
"url": "https://au.jora.com/job/Senior-Software-Engineer-abcdef1234567890abcdef1234567890",
"country": "Australia",
"search_keyword": "software engineer",
"search_location": "Sydney",
"search_page": 1,
"company": "Acme Tech",
"location": "Sydney NSW",
"salary": "$130,000 - $160,000 per year",
"job_type": "Full time",
"date_posted": "2 days ago",
"description_text": "We are looking for a Senior Software Engineer to join our platform team.",
"description_html": "<div><p>We are looking for a Senior Software Engineer to join our platform team.</p></div>",
"source": "jora",
"job_id": "abcdef1234567890abcdef1234567890",
"sponsored": false
}

Tips for Best Results

  • Start with a small limit - Use results_wanted: 20 to confirm that the keyword, country, and location return the jobs you expect.
  • Use specific keywords - Include a seniority level, skill, industry, or role variant to reduce unrelated results.
  • Choose the correct country - Select the Jora site where the relevant jobs are published.
  • Use posted_date for monitoring - A 24h, 7d, or 30d filter is useful for tracking new hiring activity.
  • Increase pages for broad searches - Raise max_pages when the first result pages do not contain enough relevant listings.
  • Review optional fields - Salary, employment type, descriptions, and company names depend on the source listing.
  • Check the dataset preview - Validate titles, locations, dates, and URLs before scheduling larger runs.
  • Report source changes - Public job pages can change. Use the Actor's Issues tab if results no longer match the expected format.

Integrations and Export Formats

  • Google Sheets - Export job records for filtering, reporting, and team review.
  • Airtable - Build a searchable hiring or market-research database.
  • Webhooks - Notify another service after an Actor run finishes.
  • Make or Zapier - Send new listings to email, CRM, Slack, or other workflow steps.
  • Apify API - Start runs and read dataset items from your own application.
  • JSON, CSV, Excel, and XML - Download results in formats suited to analysis and data pipelines.

Frequently Asked Questions

Which Jora countries are supported?

The Actor supports Australia, Hong Kong, Indonesia, Malaysia, New Zealand, and Singapore through the country input.

Can I search Jora by keyword and location?

Yes. Provide keyword and optionally set location when startUrl is empty. The Actor builds the search using the selected country site.

Can I use a direct Jora search URL?

Yes. Enter a public Jora search page in startUrl. This is useful when the search already contains the desired query and location settings.

How many jobs can I collect in one run?

Set results_wanted to the desired target from 1 to 500. The final count can be lower when the search has fewer available listings or some records cannot be collected.

How do I collect only recent job postings?

Set posted_date to 24h, 7d, or 30d. Use anytime when you want the broader available result set.

Why are salary or description fields missing?

Jora and the original employer listing do not publish every field for every job. The Actor omits unavailable optional values rather than adding misleading placeholders.

Can I schedule recurring Jora searches?

Yes. Create an Apify schedule to run the Actor hourly, daily, weekly, or at a custom interval, then send results to a webhook or another integration.

Can I export Jora jobs to CSV or Excel?

Yes. Apify datasets can be downloaded as CSV, Excel, JSON, XML, and other supported formats.

Public data collection may be subject to applicable laws, privacy requirements, and Jora's terms. You are responsible for using the Actor lawfully, respecting access restrictions, and handling job information responsibly.

Support

For questions, issues, or feature requests, use the Issues or support section on the Actor page in Apify Console.

This Actor is intended for legitimate collection and analysis of publicly available job information. Do not use collected data for unlawful discrimination, harassment, spam, or other abusive activity. Follow Jora's terms, the terms of linked source sites, and all applicable laws and privacy rules.