Middle East Jobs API - JobsIndex by Aspen Tech Labs

Access fresh job postings across the Middle East through the JobsIndex API, built by Aspen Tech Labs. Job data is sourced directly from company career pages and ATS platforms, not scraped from job boards or aggregators. Coverage spans the United Arab Emirates, Saudi Arabia, and other countries throughout the region, with coverage depth varying by country.

Use this Actor when you need job posting data centered on the Middle East rather than the full global JobsIndex feed. Search by keyword, title, company, category, salary, seniority, employment type, work arrangement, posting age, and more across the default region, with the option to add other locations through where.

Regional Coverage

The current regional dataset contains ~89,000 active jobs from 85,000+ employer career sites across 13 countries.

• United Arab Emirates (UAE): ~29,000 jobs
• Saudi Arabia: ~15,000 jobs
• Egypt: ~10,000 jobs
• Qatar: ~8,000 jobs
• Turkey: ~5,000 jobs

Need More or Something Different?

If this Actor is working well for you, we'd love a review. For more data, custom feeds, feedback, or any questions, reach out via our website or by email. You can also explore JobMarketPulse, our labor and job market intelligence platform.

Built-In Regional Preset

The intended regional preset covers the United Arab Emirates, Saudi Arabia, Qatar, Israel, Turkey, Egypt, Jordan, Kuwait, Oman, Bahrain, Lebanon, Iraq, and Cyprus.

Direct structured location inputs are not accepted because they could replace the default country scope. Use where to add locations to the default region.

Quick Start

{
  "what": "hotel OR hospitality OR restaurant",
  "size": 5
}

Input Parameters

Parameter	Description	Example
salary	Salary amount or range filter.	20h-30h
what	Job search query with keywords, boolean logic, exact phrases, or field targeting.	hotel OR hospitality OR restaurant
where	Additional field-targeted location query combined with the default regional preset using OR.	@(city) (Dubai)
title	Job title filter.	Hotel Manager
company_name	Employer name filter.	Hospitality Group
company_domain	Employer website domain.	example-hospitality.com
category	Job category.	Hotels
sub_category	More specific job function or role.	Housekeeper
industry	Employer industry.	Hotels and Restaurants
posted	Relative posting age or ISO date.	1w
employment_type	Employment type.	Full-Time
remote	Work arrangement: remote, on-site, or hybrid.	hybrid
seniority	Seniority level.	Senior
page	Page number, starting from 0.	0
size	Results per page, from 1 to 100.	5

Advanced Filters

what supports plain text, boolean logic, exact phrases, and field-targeted search.

what = hotel OR hospitality OR restaurant
what = @(title,description) (housekeeper OR bartender)

Structured Filter Precedence

When what is provided together with structured job filters such as title, company_name, company_domain, category, sub_category, industry, posted, salary, employment_type, remote, or seniority, those structured filters take priority and can override or narrow the keyword query. Use what when the corresponding structured fields are not set.

where adds locations to the internal 13-country regional preset using OR. The default regional results remain included. Use field-targeted location syntax:

where = @(city) (Dubai)
where = @(region) (Abu Dhabi)

Do not send separate country, region, city, postal_code, metro_area, county, or sub_city fields. The Actor removes those fields to protect the default country scope. User-provided where values are always appended with OR; they can add locations but cannot remove or replace the default Middle East preset.

Example with an additional city query:

{
  "what": "software engineer",
  "where": "@(city) (Dubai)",
  "size": 5
}

Salary Filter Format

Use NUMBER[UNIT] or NUMBER[UNIT]-NUMBER[UNIT]. Supported units are h, d, w, m, and y.

Limits and Pagination

This Actor uses the JobsIndex jobs API. Results are paginated with page and size.

Parameter	Default	Min	Max
page	0	0	Depends on size and the item cap
size	5	1	100

Invalid page or size values can return 400 Invalid page or size parameters.

Item Caps

Query shape	Max items	Effective max size	Over-size behavior
No company filter	1000	100	Validation error; not silently capped
Company filter plus another keyword or filter	20	20	Silent cap with capping metadata
Company filter only	5	5	Silent cap with capping metadata

A company filter means company_name, company_domain, or a company field referenced inside what. Another keyword or filter means anything in what other than company_*, or a value in fields such as title, category, sub_category, industry, posted, salary, employment_type, remote, or seniority.

This Actor always applies an internal regional where preset, so company-filtered requests normally use the 20-item company|keywords cap.

When a company-filtered request asks for size greater than the effective cap, the API returns up to the capped number of results instead of erroring. Response metadata includes size_requested and size_capped_by: "company" for the 5-item cap or "company|keywords" for the 20-item cap. These fields are absent from uncapped responses.

No-company-filter requests are not silently capped. Requests beyond the 1000-item retrieval window can return 400 Item limit reached. Maximum of 1000 items can be retrieved.

Free-Text Query Limits

The user-facing what and where queries are subject to JobsIndex free-text limits. The effective upstream where expression includes the default regional preset and the OR wrapper.

Limit	Value	Error behavior
User-entered what length	700 characters	400 parameter exceeds 700 characters
User-entered where length	511 characters	Input validation error or 400 parameter exceeds 700 characters for the combined query
Effective upstream where length	700 characters, including the regional preset	400 parameter exceeds 700 characters
Excessive MATCH operators	Backend safety limit	400 Too many MATCH operators
Unsafe SQL-like keywords	blocked	400 Unsafe MATCH expression

Field Validation

Invalid filter values can return 400 Invalid value for parameter: <name>. Common validation examples include malformed company domains, invalid dates or relative posted values, invalid salary format, unsupported location formats, or overly long field values.

Output

Each run stores job records in the default Apify dataset. The dataset schema includes an Overview table for the most useful fields and a Raw data (all fields) table for the complete JobsIndex record.

Example dataset item:

{
  "id": "example-middle-east-job-id",
  "title": "Housekeeper",
  "title_raw": "Hotel Housekeeping Attendant",
  "company_name": "Example Hospitality Group",
  "company_domain": "example-hospitality.com",
  "company_type": "company",
  "category": "Hotels",
  "sub_category": "Housekeeper",
  "industry": "Hotels and Restaurants",
  "country": "United Arab Emirates",
  "region": "Dubayy",
  "city": "Dubai",
  "salary_value": "18000.00-25000.00",
  "salary_currency": "AED",
  "salary_unit": "MONTH",
  "employment_type": "Full-Time",
  "remote": "on-site",
  "posted": "2026-08-01",
  "url_source": "https://example-hospitality.com/careers/housekeeper",
  "url_apply": "https://example-hospitality.com/careers/housekeeper/apply"
}

Field availability depends on the source job posting.