# Naukrigulf Jobs Scraper (`thenetaji/naukrigulf-jobs-scraper`) Actor

Search Naukrigulf by keyword and city across the UAE, Saudi Arabia, Qatar and the Gulf, filter by experience and posting age, and export each job with company, skills, description and dates.

- **URL**: https://apify.com/thenetaji/naukrigulf-jobs-scraper.md
- **Developed by:** [The Netaji](https://apify.com/thenetaji) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.85 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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 Jobs Scraper

The Actor searches Naukrigulf.com, the Gulf job board, by keyword and location and saves each matching job as one dataset row with its title, company, city, country, experience range, skills, summary, full description and posting time. Results arrive in Naukrigulf's relevance order by default, and the experience and posting-age filters narrow a search the same way they do on naukrigulf.com.

```json
{
  "query": "accountant",
  "location": "Dubai",
  "experienceYears": 3,
  "postedWithinDays": "7",
  "sort": "relevance",
  "maxItems": 100
}
```

### Accepted input

- `query` is required: a job title, skill or keyword such as `accountant` or `site engineer`.
- `location` is optional and takes a city or country as Naukrigulf spells it, for example `Dubai`, `Abu Dhabi`, `Riyadh` or `Qatar`.
- `experienceYears` keeps jobs open to a candidate with that many years of experience; it is empty by default, which means any experience.
- `postedWithinDays` accepts `any`, `1`, `3`, `7`, `15`, `30` or `60`; the default is `any`.
- `sort` accepts `relevance` (the default) or `date` (newest first).
- `enrichJobDescription` adds each saved job's full posting to its row; it is off by default. See [Full postings](#full-postings).
- `page` is the first result page to read; it defaults to `1`.
- `maxItems` bounds the number of saved rows; it defaults to `100`, and `0` removes the bound.

### Response fields

Each row carries `job_id`, `title`, `url`, `company` (`name`, `id`, `url`, `logo_url`), `job_location` as Naukrigulf prints it, `city` and `country` where the posting names them, `experience` (`min_years`, `max_years`, `label`), `skills`, `summary`, `highlights`, `description_html`, `posted_at` as an ISO 8601 timestamp in UTC, `vacancies`, and the flags `is_easy_apply`, `is_sponsored`, `is_consultant` (posted by a recruitment consultancy) and `is_confidential_company`. Every row also records the `query`, `location` and `page` it was collected under, together with Naukrigulf's own `total` and `total_vacancies` for the search and the `search_url`.

Naukrigulf's search results carry no salary. The full-posting option adds it where the employer publishes one.

### Full postings

With `enrichJobDescription` on, the Actor also reads each saved job's own posting and adds `salary` (`min`, `max`, `currency`, `disclosed`), `employment_type`, `work_mode` (`office`, `remote` or `hybrid`), `industry`, `functional_area` and `candidate` (`profile_html`, `education`, `nationality`, `gender`), plus the company's `profile` and `type`. A hidden salary comes back with `disclosed` set to `false` and no figures, never as zero. Each posting is a further request, so a run takes longer, and each posting read is billed as a separate event. A posting that has closed since the search keeps its search row unchanged and is not billed.

Recruiter names and contact details on a posting are not collected.

### Behaviour on large searches

Naukrigulf serves 30 jobs per page and up to 1,500 pages for one search. The run follows the results to their last page, or to `maxItems`, and stops cleanly there. A search with no match returns no rows rather than unrelated jobs.

### Notes on the results

**Why is relevance the default instead of newest first?**
Naukrigulf matches a search more loosely in date order. On the first page of "accountant", relevance order had the term in the title or keywords of 26 of 30 jobs; date order had it in 3.

**Why are `city` and `country` empty on some rows, and why does `city` sometimes list several cities?**
Both are read from Naukrigulf's own location text, such as "Abu Dhabi - United Arab Emirates (UAE)". A posting in several cities of one country keeps them together, so "Dubai, Abu Dhabi - United Arab Emirates (UAE)" gives the `city` "Dubai, Abu Dhabi". Text with no country part, or with more than one, stays in `job_location` and leaves the two fields empty rather than guessing. To filter on one city, match it inside `city` rather than comparing the whole value.

### Related Actors

[Naukri Jobs Scraper](https://apify.com/thenetaji/naukri-jobs-scraper) runs the same kind of search on Naukri.com in India.

# Actor input Schema

## `query` (type: `string`):

The job title, skill or keyword to search for.

## `location` (type: `string`):

A city or country as Naukrigulf spells it, such as Dubai, Abu Dhabi, Riyadh or Qatar. Left empty, the search covers every location.

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

Keep jobs open to someone with this many years of experience. Leave empty for any.

## `postedWithinDays` (type: `string`):

Keep jobs posted within this many days.

## `sort` (type: `string`):

Relevance keeps to jobs that match the search. Newest first matches it loosely: on page 1 of "accountant", 3 of 30 jobs by date had the term, against 26 of 30 by relevance.

## `enrichJobDescription` (type: `boolean`):

Reads each saved job's own posting and adds what a search row does not carry: the salary where the employer publishes it, the employment type, the work mode, the industry and functional area, the candidate requirements (education, nationality, gender and the employer's own profile text) and the company's profile and type.

It costs one further request per job, so a run is slower with it on, and it is billed per posting read.

## `page` (type: `integer`):

Which result page to start from. Naukrigulf serves 30 jobs a page.

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

Maximum number of rows to save. Set 0 for no limit.

## Actor input object example

```json
{
  "query": "accountant",
  "location": "Dubai",
  "experienceYears": 3,
  "postedWithinDays": "any",
  "sort": "relevance",
  "enrichJobDescription": false,
  "page": 1,
  "maxItems": 20
}
```

# Actor output Schema

## `dataset` (type: `string`):

All records scraped by this run

# 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 = {
    "query": "accountant",
    "location": "Dubai",
    "page": 1,
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("thenetaji/naukrigulf-jobs-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 = {
    "query": "accountant",
    "location": "Dubai",
    "page": 1,
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("thenetaji/naukrigulf-jobs-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 '{
  "query": "accountant",
  "location": "Dubai",
  "page": 1,
  "maxItems": 20
}' |
apify call thenetaji/naukrigulf-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thenetaji/naukrigulf-jobs-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/qcWhBhfZoFJo1jPBs/builds/K1kV90gbazjHdTdYR/openapi.json
