Bayt Jobs Data Scraper for MENA Listings

Turn a Bayt keyword, market, category, listing URL, or job-detail URL into structured job records for recruiters, labor-market researchers, sourcing teams, and AI agents. Each row can include the job title, company, city, country, listing snippet, Bayt job ID, apply URL, source query, source market, source URL, and collection time.

Best fit for this Actor

• Choose this Actor for focused Bayt research across MENA markets using keyword, category, or direct URL inputs.
• Use country-specific searches when the research brief is tied to a local hiring market, or use the international market for regional discovery.
• For a cross-platform hiring brief, start with the Multi-Platform Jobs Scraper, then use this Actor for a focused Bayt dataset.

From a hiring question to a reviewable shortlist

A talent researcher starts with a role keyword and a target Bayt market. The Actor builds the matching listing route, collects job cards until the requested scope is reached, and returns source-linked rows. The researcher then groups openings by company and location, opens selected applyUrl values for review, and retains searchQuery, sourceCountry, and sourceUrl to explain how every record entered the shortlist.

Quick start input

{
  "searchQuery": "software engineer",
  "country": "uae",
  "maxResults": 50
}

For category-led collection, provide a real Bayt category slug in jobCategory. For a known listing page or job page, provide startUrls; that route becomes the starting point for the run.

Input reference

Field	Type	What it controls
searchQuery	string	Free-text role or skill query used to create a Bayt search.
country	string	Bayt market and localized listing route.
jobCategory	string	Bayt category slug for category-led collection.
startUrls	array	Public Bayt listing or job-detail pages supplied directly.
maxResults	integer	Stable dataset cap for a focused run.
proxyConfiguration	object	Apify proxy route used for Bayt pages.

What data you receive

One dataset row represents one Bayt job listing discovered by the selected search, category, listing page, or detail page.

Field	Meaning
jobTitle	Job title displayed by Bayt.
companyName	Hiring organization name.
location, city, country	Display location plus normalized geography.
snippet	Listing-card description preview.
applyUrl	Public Bayt job detail or apply page.
jobId	Bayt identifier parsed from the job URL.
searchQuery, sourceCountry	Search context echoed into the row.
sourceUrl, scrapedAt	Listing provenance and collection time.

{
  "jobTitle": "Software Engineer",
  "companyName": "Example Company",
  "location": "Dubai, United Arab Emirates",
  "city": "Dubai",
  "country": "United Arab Emirates",
  "snippet": "Build and maintain customer-facing applications.",
  "applyUrl": "https://www.bayt.com/en/uae/jobs/example-job-12345/",
  "jobId": "12345",
  "searchQuery": "software engineer",
  "sourceCountry": "uae",
  "sourceUrl": "https://www.bayt.com/en/uae/jobs/software-engineer-jobs/",
  "scrapedAt": "2026-06-02T09:00:00.000Z"
}

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~bayt-jobs-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "searchQuery": "software engineer",
    "country": "uae",
    "maxResults": 50
  }'

Read the default dataset after completion to receive the structured job rows.

Use with AI agents through Apify MCP

Search Bayt for software engineering roles in the selected MENA market. Return title, company, city, country, snippet, apply URL, source query, source URL, and collection time. Keep the scope bounded, read the dataset after completion, group the results by company and location, and retain provenance beside each recommendation.

An agent can route confidently when the prompt includes the target role, market, desired scope, and output fields. Ask it to inspect the outcome, read the dataset, preserve source URLs, and keep cost aligned with the requested maxResults.

Connect the workflow

Use the Multi-Platform Jobs Scraper when the research question spans several job sources. Continue with this Bayt Actor when the next step calls for focused MENA listings and Bayt apply URLs.

Pricing

This Actor uses Pay per event plus Apify platform usage. Open the live Pricing tab for current event details, and use maxResults with Apify run cost controls to keep each search aligned with your budget.

Best results

• Use a specific role, skill, or category that matches the hiring brief.
• Select the Bayt market that matches the desired geography.
• Supply a canonical public listing URL when a saved Bayt search already represents the brief.
• Keep sourceUrl, searchQuery, and sourceCountry with every downstream shortlist or analysis.

Builder's note

I designed each job row to echo its query, market, and source URL because I found that a title and company alone are too easy to separate from the search intent that produced them. Keeping the discovery context beside the apply URL makes agent summaries, spreadsheet review, and later reruns much easier to reason about.

Responsible use

Use public job data for authorized research and recruitment workflows, and handle employer and applicant-related information in line with applicable laws, Bayt terms, and your organization's hiring policies.