# Naukrigulf Scraper: Gulf Jobs, Salaries and New Job Alerts (`datahamster/naukrigulf-scraper`) Actor

Naukrigulf scraper for Gulf and Middle East jobs (UAE, Saudi Arabia, Qatar, Kuwait, Oman, Bahrain, Egypt). Many keywords and locations per run, country, industry, experience and salary filters, salary as numbers, no start fee. Monitor mode returns only new jobs.

- **URL**: https://apify.com/datahamster/naukrigulf-scraper.md
- **Developed by:** [Viktor Dubnytskiy](https://apify.com/datahamster) (community)
- **Categories:** Jobs
- **Features:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 result items

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Naukrigulf Scraper

Search Naukrigulf, the Gulf and Middle East job board (UAE, Saudi Arabia, Qatar, Kuwait, Oman, Bahrain, Egypt and more), by keyword and location and get one flat row per job: title, company, cities and country, experience range in years, vacancies, posted date in ISO UTC and the site's summary and highlights. Turn on `includeDetails` for salary as numbers (min, max, currency, monthly), the full description, industry, education, employment and workplace type. No account, no cookies, no start fee. Monitor mode turns the same search into an alert on new jobs.

**Try it:** the prefilled example (`accountant` in `Dubai`, 20 jobs) runs in about 5 seconds. Results cost $1.00 per 1,000, with no per-run start fee.

**Why this one** (compared with the most-used Naukrigulf actor in the Store, blackfalcondata/naukrigulf-scraper, 277 users in 30 days; its input schema and README checked 2026-11-13):

- **No start fee.** $0.001 per job and nothing per run. The most-used actor charges the same $0.001 per job plus $0.005 every time a run starts, which doubles the cost of a 5-job run and adds $1.50 a month to a search scheduled 10 times a day.
- **Country, industry and salary-band filters.** `countries` (several at once), `industries` and `salaryBandsUsd` are sent to Naukrigulf as its own filters. The most-used actor's input has `location` (one city or country), `datePosted` and `experienceYears`, and no industry or salary filter (its README says a salary filter in a pasted search URL is not applied).
- **Many keywords and locations in one run.** Every keyword is searched in every location, each search gets a fair share of `maxItems` (a share a small search leaves unused goes to the others), and a job found twice is returned once. The most-used actor takes one location per run, and several keywords only as a comma list in one query; it has no keyword x location grid (other combinations need pasted search URLs).
- **No contact persons in the data.** Rows hold the job and the hiring company. The recruiter's name, e-mail, phone and address on the job page are never read, and the description is cut at the ad's application block ("To apply", "Send your CV", "Interested candidates ..."). The most-used actor's output includes `contactName`, `contactDesignation` and `contactEmail`, which is personal data you then have to handle under GDPR and similar laws.

### What you get

Real rows from the example dataset (`keywords: ["accountant"]`, `locations: ["Dubai"]`, run Ug1Q5Sp9xzxJKIhwF, 20 jobs, 5.0 s):

| title / company | location | experience | posted |
|---|---|---|---|
| AP Accountant / Al Abbas Group | Dubai | 0-3 years | 2026-11-11 |
| Senior Accountant / BRONZE HQ DISTRIBUTION AND TRADING  FZE | Dubai | 7-11 years | 2026-11-11 |
| Assistant Accountant / Tableegh | Dubai | 1-2 years | 2026-11-13 |
| Accounts & Admin / Go Global Migration L.L.C F.Z | Dubai | 0-1 years | 2026-11-11 |
| Accountant / Spike Gold | Dubai | 1-3 years | 2026-11-11 |

One full row with `includeDetails: true` (run kogc0m7ecIl35kGIS; description shortened here):

```json
{
  "id": "111126000159",
  "url": "https://www.naukrigulf.com/accounts-admin-jobs-in-dubai-uae-in-go-global-migration-l-l-c-f-z-0-to-1-year-n-cd-382751-jid-111126000159",
  "scrapedAt": "2026-11-13T21:54:14.077772Z",
  "jobId": "111126000159",
  "title": "Accounts & Admin",
  "companyName": "Go Global Migration L.L.C F.Z",
  "companyId": "382751",
  "companyLogoUrl": null,
  "location": "Dubai - United Arab Emirates (UAE)",
  "cities": [
    "Dubai"
  ],
  "countries": [
    "United Arab Emirates (UAE)"
  ],
  "experienceMin": 0,
  "experienceMax": 1,
  "vacancies": 1,
  "postedAt": "2026-11-11T08:38:13Z",
  "snippet": "Manage accounts payable and receivable, reconcile statements, prepare financial reports, oversee payroll, requiring a degree in Accounting or Finance.",
  "highlights": [
    "Manage day-to-day accounts payable and receivable",
    "Reconcile bank statements and general ledger accounts",
    "Prepare financial reports for management review",
    "Oversee payroll processing and tax compliance"
  ],
  "isWebJob": false,
  "isTopEmployer": false,
  "isFeaturedEmployer": false,
  "isPremium": false,
  "isSponsored": false,
  "salaryMin": 2500,
  "salaryMax": 3000,
  "salaryCurrency": "AED",
  "salaryPeriod": "month",
  "salaryHidden": false,
  "description": "Manage day-to-day accounts payable and receivable, ensuring timely processing of invoices and payments.\nReconcile bank statements and general ledger accounts...",
  "descriptionTruncated": false,
  "desiredCandidate": "Associate's or Bachelor's degree in Accounting, Finance, or Business Administration.",
  "companyDescription": null,
  "industry": "Other",
  "functionalArea": "Accounts / Taxation / Audit / Company Secretary",
  "education": "Any Graduation",
  "nationality": "Indian",
  "employmentType": "Full-time",
  "workplaceType": "On-site",
  "jobCountry": "United Arab Emirates (UAE)",
  "jobSource": "POSTED",
  "applyUrl": null,
  "isConsultantJob": false,
  "isConfidentialCompany": false,
  "isExpired": false,
  "detailsFetched": true,
  "query": "accountant",
  "searchLocation": "Dubai",
  "rank": 4
}
```

`salaryMin` / `salaryMax` are monthly amounts in `salaryCurrency` (Naukrigulf labels the field "Monthly Salary"). They are read from the job page, so they need `includeDetails`; in our runs 18 of 46 jobs with job pages had salary numbers (16 of 30 accountant jobs in Dubai and Riyadh, 2 of 16 software engineer jobs in the UAE and Qatar); `salaryHidden: true` means the employer did not disclose it. `postedAt` is the date the ad was last posted; employers can refresh an ad and move it. `experienceMin` / `experienceMax` are years. `cities` and `countries` are split from the site's location text. `jobSource` is POSTED for ads placed on Naukrigulf (also IMS, TAG, FBA for other in-house channels) and WEB for jobs imported from a company careers site; for WEB jobs `applyUrl` is that careers-site link. `isWebJob` is the search card's flag.

### Use cases

- Get a morning alert with only the new Naukrigulf jobs for your role in Dubai, Riyadh or Doha.
- Compare advertised monthly salaries for a role across Gulf countries.
- Track which companies hire for a role and in which industries.
- Feed a job board, newsletter or spreadsheet with fresh Gulf jobs.

### Try it

Prefilled input: `keywords: ["accountant"]`, `locations: ["Dubai"]`, 20 jobs.

```json
{"keywords": ["accountant", "auditor"], "locations": ["Dubai", "Riyadh"], "postedWithin": "7d", "includeDetails": true, "maxItems": 100}
```

```json
{"keywords": ["software engineer"], "countries": ["UAE", "Qatar"], "industries": ["IT"], "experienceYears": 3, "salaryBandsUsd": ["3001-4000", "4001-5000"]}
```

Monitor (schedule it daily or hourly as a task):

```json
{"mode": "monitor", "keywords": ["accountant"], "locations": ["Dubai"], "maxItems": 50}
```

### Input

- `keywords`, `locations`: searches are every keyword in every location. Without keywords the search lists jobs by the other filters only, and imported jobs come after all jobs posted on Naukrigulf (see Limits).
- `countries`: the site's country filter, several at once.
- `industries`: the site's industry filter (the 26 largest industries).
- `experienceYears`: jobs whose required range includes this number of years.
- `postedWithin`: last day, 3, 7, 15 or 30 days.
- `salaryBandsUsd`: the site's monthly salary bands in US dollars.
- `sortBy`: relevance or newest first.
- `includeDetails`: job page fields, including salary numbers. One extra request per job.
- `maxResultsPerSearch`: depth of each search, 50 jobs per page.
- `mode: "monitor"`, `monitorStateId`, `webhookUrl`, `telegramBotToken` / `telegramChatId`: see Monitor mode.

### Monitor mode

Run the same input as a scheduled task with `mode: "monitor"`. Each search is read newest first. The first run of each search is a baseline: it records the first 200 jobs (or `maxResultsPerSearch`), reads no job pages and charges only the check. Later runs return only jobs the monitor has not seen and stop at the first page made only of known jobs, so a quiet day costs one page per search. A Naukrigulf job id starts with the day it was created (DDMMYY); an unseen job created more than 2 days before the newest job of the last run (an older ad the employer refreshed to the top) is recorded without being returned. A page made only of such refreshed older ads does not end the check: up to 3 such pages are read past. A job returned without its details (job page refused) is completed on a later run at no charge. Measured: baseline of 397 jobs in two searches (accountant and nurse in Dubai) with `includeDetails` on, no job page read, $0.0007 usage (run NxgvNy4l9j5QVd1I1); the next run read 1 page per search, 0 new, $0.0005 usage (PaB1mbDcPMkA2tDzh).

### Pricing

Pay per event, platform usage paid by you:

- `result`: $0.001 per job (scrape mode).
- `monitor-check`: $0.005 per monitor run.
- `change`: $0.001 per new job in monitor mode.

Platform usage, measured on our runs at 512 MB without proxy: the 20-job example $0.00043 (4.5 s); 400 jobs in four searches $0.0030 (about $0.008 per 1,000 jobs on top of the result price, 28 s); `includeDetails` about $0.03-0.04 per 1,000 jobs (60 jobs with job pages in four searches $0.0018, 47 s); a monitor baseline of 200 jobs $0.0006; a monitor check with nothing new $0.0005.

Store discounts: SILVER 10% off, GOLD and above 20% off. If you find a problem, please open an issue; if it works for you, a review helps.

### Related actors

- [Bayt Jobs Scraper](https://apify.com/datahamster/bayt-jobs)
- [LinkedIn Jobs Scraper](https://apify.com/datahamster/linkedin-jobs-scraper)
- [Indeed Scraper](https://apify.com/datahamster/indeed-scraper)
- [Career Site Jobs Monitor](https://apify.com/datahamster/ats-jobs)

### Limits

- Salary numbers come only from job pages (`includeDetails`); search results carry no salary. Most Naukrigulf employers hide the salary: in our runs 28 of 46 job pages had no salary numbers.
- The salary band filter (`salaryBandsUsd`) uses the employer's range as the site files it, including hidden ones, so jobs it returns often have no salary numbers.
- `industries` lists the 26 largest Naukrigulf industries; smaller ones are not offered.
- The site serves a search up to 45,000 jobs deep (50 per page). Split very broad searches by keyword, location or country.
- Keyword search is the site's own and is broad: it matches related titles and skills, not only the exact phrase.
- Naukrigulf ignores a location it does not know and treats the word as part of the keyword ("Atlantis" returned the same 6,843 accountant jobs as no location). The actor detects this (the site's breadcrumb names no place and the location did not cut the number of jobs; one extra request per keyword, only when needed), returns nothing for that search and names the place in the run log, the status message and `NAUKRIGULF_STATS.unknownLocations`. Spellings the site resolves itself work: "Kuwait City", "Abu-Dhabi", "Doha, Qatar", "Dubai, UAE".
- The site reads "KSA" as Kuwait; the actor sends "Saudi Arabia" instead (also "RAK" as "Ras Al Khaimah", "Mecca" as "Makkah", "Medina" as "Madinah"). `searchLocation` keeps your spelling.
- Without a keyword, Naukrigulf lists every job posted on the site itself before any job imported from a company careers site (`jobSource` WEB; in a newest-first search of all jobs on 2026-11-13 the first one was at position 937). A search without keyword therefore returns few WEB jobs, and a monitor without keyword does not report new WEB jobs (the run log and status say so). Use keywords to get them: with a keyword both kinds are mixed (16 of 60 rows were WEB jobs in our run 3MThX4FIkvLwYTG3A, 0 of 200 in a newest-first search without keyword, 20iHuVf177YWKpf2U).
- Monitor: if more than `maxResultsPerSearch` (200 by default) new jobs appear in one search between two runs, the run returns the first 200 and the rest are not read; schedule the task more often for very broad searches. A job created more than 2 days before it first appears in the date order is recorded silently.
- The description keeps the job text up to the ad's application block; `descriptionTruncated` is true when that block was cut. E-mail addresses, phone numbers, WhatsApp chat links and contact names are also removed from the rest. Naukrigulf already masks most contacts itself (it prints `EMAIL_ADDRESS`), which stays in the text.
- The actor uses the JSON API the Naukrigulf website calls. If Naukrigulf changes it, a run ends with `emptyReason: blocked` or `source_changed`, not with an empty success.

### FAQ

**Do I need a Naukrigulf account?** No. The actor reads the public job search.

**Why is the salary empty for most jobs?** The employer chose not to disclose it (`salaryHidden: true`). Turn on `includeDetails`, salaries are only on job pages.

**Can I get the recruiter's name, e-mail or phone?** No. Rows hold the job and the hiring company, not people.

**Which currencies?** The one the employer used: AED, SAR, QAR, KWD, OMR, BHD, USD and others.

### Changelog

- 0.1 (2026-11-13): first version.

# Actor input Schema

## `keywords` (type: `array`):

Job keywords, one per line, e.g. "accountant", "python developer", "nurse". Each keyword is searched in each location below. Leave empty to list jobs by the other filters only; note that without a keyword Naukrigulf lists jobs imported from company career sites only after all jobs posted on Naukrigulf itself, so a search (or monitor) without keyword misses most of them.

## `locations` (type: `array`):

Cities or countries the way Naukrigulf's location box takes them, one per line, e.g. "Dubai", "Riyadh", "Doha", "Saudi Arabia". Every keyword is searched in every location. Leave empty for all locations. Use the site's spelling; "KSA", "RAK", "Mecca" and "Medina" are sent as "Saudi Arabia", "Ras Al Khaimah", "Makkah" and "Madinah" (the site itself reads KSA as Kuwait). A place the site does not know is ignored by the site; the actor then returns nothing for that search and names the place in the log and status.

## `countries` (type: `array`):

Keep only jobs in these countries (the site's country filter; several allowed), e.g. \["UAE", "Qatar"]. Combines with locations. Empty = all countries.

## `industries` (type: `array`):

Keep only jobs of these industries (the site's industry filter), e.g. \["IT", "Banking and Finance"]. Empty = all.

## `experienceYears` (type: `integer`):

Keep only jobs whose required experience range includes this number of years (the site's filter, checked again on every row). Example: 3 keeps a 2-5 years job and drops a 5-10 years job. Empty = any.

## `postedWithin` (type: `string`):

Keep only jobs posted in this window (the site's freshness filter). The site keeps jobs for about 60 days. Example: 7d.

## `salaryBandsUsd` (type: `array`):

Keep only jobs in these monthly salary bands, in US dollars (the site's salary filter). The site files a job under the employer's range even when the employer hides the figure, so many matching jobs have no salary numbers. Example: \["2001-3000", "3001-4000"]. Empty = any salary.

## `sortBy` (type: `string`):

Order of the site's results. Monitor mode always reads newest first. Example: date.

## `includeDetails` (type: `boolean`):

Read each job's page too: salary as numbers (min, max, currency, monthly), full description, desired candidate, company description, industry, functional area, education, employment and workplace type, apply URL of imported jobs. One extra request per job.

## `maxResultsPerSearch` (type: `integer`):

How deep each keyword x location search reads (50 jobs per page). Empty = 1,000 in scrape mode, 200 in monitor mode. The site serves at most 45,000 jobs per search.

## `maxItems` (type: `integer`):

Stop after this many results (you are charged only for pushed items)

## `mode` (type: `string`):

scrape = full results; monitor = only new/changed items since the previous run of this task

## `monitorStateId` (type: `string`):

Optional state id when not running as a saved task (monitor mode)

## `webhookUrl` (type: `string`):

POST a change summary here in monitor mode

## `telegramBotToken` (type: `string`):

Optional: bot token for monitor-mode change summaries

## `telegramChatId` (type: `string`):

Optional: chat id that receives monitor-mode summaries

## Actor input object example

```json
{
  "keywords": [
    "accountant"
  ],
  "locations": [
    "Dubai"
  ],
  "postedWithin": "any",
  "sortBy": "relevance",
  "includeDetails": false,
  "maxItems": 20,
  "mode": "scrape"
}
```

# Actor output Schema

## `results` (type: `string`):

All pushed rows (dataset, JSON)

## `resultsTable` (type: `string`):

Dataset in the Console viewer

## `runSummary` (type: `string`):

RUN_SUMMARY record

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "accountant"
    ],
    "locations": [
        "Dubai"
    ],
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("datahamster/naukrigulf-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": ["accountant"],
    "locations": ["Dubai"],
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("datahamster/naukrigulf-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "accountant"
  ],
  "locations": [
    "Dubai"
  ],
  "maxItems": 20
}' |
apify call datahamster/naukrigulf-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datahamster/naukrigulf-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/h9BHOmu5d57udBtQj/builds/evyy2cMOolcIsNJfD/openapi.json
