# Indeed Job Radar Actor (`vjkhush/indeed-job-radar-actor`) Actor

Indeed crawler actor for normalized job listings. Private deployment.

- **URL**: https://apify.com/vjkhush/indeed-job-radar-actor.md
- **Developed by:** [Richard v](https://apify.com/vjkhush) (community)
- **Categories:** AI, Jobs, Automation
- **Stats:** 3 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 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.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Indeed Job Radar

Scrape Indeed job listings across **60+ country markets** with full descriptions, qualifications, benefits, salary data, and employment type. No login or API key required.

Fast two-phase architecture: lightweight HTTP requests scan listing pages, headless browser visits only detail pages. Listing-only mode finishes in seconds.

### Why use this actor?

- **60+ countries** — US, UK, Germany, Canada, Australia, India, France, and 55 more Indeed domains
- **Full job details** — descriptions, qualifications, benefits, and employment type from each job page
- **Server-side filters** — job type, experience level, and posting date applied at the URL level before crawling, reducing blocks and wasted requests
- **Client-side filters** — salary range, company name, company rating, remote/hybrid, and posting freshness
- **Two speeds** — detail scraping ON for full data, or OFF for a fast title+URL scan
- **Graceful timeout** — partial results always saved, even if the run hits the Apify timeout

### Output fields

Each result includes:

| Field | Example |
|---|---|
| `job_id` | `a1b2c3d4e5f6g7h8` |
| `title` | `Software Engineer` |
| `company` | `Google 4.3` |
| `location` | `New York, NY` |
| `salary` | `$120,000 - $160,000 a year` |
| `employment_type` | `Full-time` |
| `posted_at` | `2 days ago` |
| `description` | Full job description (1,000 - 10,000+ chars) |
| `qualifications` | Qualifications section from the job page |
| `benefits` | Benefits section from the job page |
| `url` | Direct Indeed job URL |
| `source` | `indeed` |
| `scraped_at` | ISO timestamp |

Turn off **Scrape job details** to skip the detail page visit. You get titles, companies, salaries, and URLs much faster but without full descriptions.

### How to use

#### Quick search with full details

```json
{
  "keywords": ["Software Engineer"],
  "locations": ["New York"],
  "country": "US",
  "maximumItems": 5,
  "scrapeDetails": true
}
```

#### Multi-keyword job monitoring

```json
{
  "keywords": [
    "cyber security",
    "information security",
    "soc analyst",
    "security engineer"
  ],
  "locations": ["Germany"],
  "country": "DE",
  "publicationAge": "LAST_3_DAYS",
  "jobType": "fulltime",
  "maximumItems": 200,
  "maxListingPages": 20
}
```

#### Fast listing scan (no detail pages)

```json
{
  "keywords": ["Data Analyst"],
  "locations": ["London"],
  "country": "GB",
  "maximumItems": 100,
  "scrapeDetails": false,
  "publicationAge": "LAST_7_DAYS",
  "experienceLevel": "entry_level"
}
```

### Filters

#### Server-side (applied via URL parameters)

| Filter | Options |
|---|---|
| **Job type** | Full-time, Part-time, Contract, Temporary, Internship |
| **Experience level** | Entry, Mid, Senior |
| **Posting freshness** | Today, 24h, 3 days, 7 days, 14 days, 30 days |

#### Client-side (applied after parsing)

| Filter | Description |
|---|---|
| **Salary range** | Min/max salary parsed from listing text |
| **Company name** | Substring match |
| **Company rating** | Minimum star rating |
| **Remote-first** | Keeps only remote/hybrid listings |
| **Include no-salary jobs** | Toggle to exclude listings without salary |

### Supported markets

60+ Indeed country domains including:

US, GB, CA, AU, IN, DE, FR, NL, IE, SG, AE, AR, AT, BH, BE, BR, CH, CL, CN, CO, CR, CZ, DK, EC, EG, ES, FI, GR, HK, HU, ID, IL, IT, JP, KR, KW, LU, MA, MX, MY, NG, NO, NZ, OM, PA, PE, PH, PK, PL, PT, QA, RO, SA, SE, TH, TR, TW, UA, UY, VE, VN, ZA

The proxy country automatically matches your selected market for best results.

### Performance

| Mode | Speed | Data |
|---|---|---|
| **Detail scraping ON** (default) | ~2-3 min for 50 jobs | Full descriptions, qualifications, benefits |
| **Detail scraping OFF** | ~10-20 sec for 100 jobs | Titles, companies, salaries, URLs only |

Use **Job type** and **Experience level** filters to reduce crawl volume at the server level.

The actor gracefully stops before the Apify timeout, so partial results are always saved even on large runs.

### Integrations

- **n8n / Make / Zapier** — schedule runs and push results to Google Sheets, Airtable, or databases
- **Telegram / Slack / Discord** — send alerts for new job postings matching your criteria
- **Google Sheets / Airtable** — export structured data for tracking and analysis
- **Custom APIs** — use webhooks to trigger downstream workflows on each run

### How it works

The actor uses a two-phase crawl:

1. **Listing phase (CheerioCrawler)** — fast HTTP-only requests parse search result pages. No browser overhead, minimal detection risk.
2. **Detail phase (PlaywrightCrawler)** — headless browser visits each job page to extract the full description, qualifications, benefits, and employment type from JavaScript-rendered content.

This hybrid approach keeps listing scans fast while still extracting complete job data when needed.

# Actor input Schema

## `country` (type: `string`):

Choose the Indeed site to search. 60+ countries supported.

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

Add one or more role/skill keywords.

## `keyword` (type: `string`):

Optional fallback keyword. Comma-separated values are also supported.

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

City, region, or country names.

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

Optional fallback location. Comma-separated values are supported.

## `scrapeDetails` (type: `boolean`):

Visit each job page to get the full description, qualifications, benefits, and employment type. Slower but much more data.

## `jobType` (type: `string`):

Filter by employment type (server-side Indeed filter).

## `experienceLevel` (type: `string`):

Filter by experience level (server-side Indeed filter).

## `publicationAge` (type: `string`):

Filter by posting recency. Applied both as a URL parameter (server-side) and as a client-side check.

## `maximumItems` (type: `integer`):

Maximum number of jobs to output.

## `radius` (type: `integer`):

Search radius around location.

## `companyName` (type: `string`):

Optional company name filter.

## `remoteWork` (type: `boolean`):

Keep only jobs that look remote/hybrid.

## `includeNoSalaryJobs` (type: `boolean`):

Enable to keep listings without salary text.

## `minimumSalary` (type: `integer`):

Minimum salary filter (best effort from listing text).

## `maximumSalary` (type: `integer`):

Maximum salary filter.

## `minimumRating` (type: `number`):

Minimum company rating found in listing text.

## `maxListingPages` (type: `integer`):

Maximum listing pages to crawl per keyword+location combo. Each page has ~15 results.

## `maxConcurrency` (type: `integer`):

Crawler concurrency.

## `maxRequestRetries` (type: `integer`):

Retries per request before failing.

## `minListingDelayMs` (type: `integer`):

Minimum pause before parsing list pages.

## `maxListingDelayMs` (type: `integer`):

Maximum pause before parsing list pages.

## `proxyConfiguration` (type: `object`):

Proxy setup. Residential proxies recommended for stability.

## Actor input object example

```json
{
  "country": "US",
  "keywords": [
    "Software Engineer"
  ],
  "keyword": "",
  "locations": [],
  "location": "",
  "scrapeDetails": true,
  "jobType": "",
  "experienceLevel": "",
  "publicationAge": "ALL",
  "maximumItems": 50,
  "radius": 30,
  "companyName": "",
  "remoteWork": false,
  "includeNoSalaryJobs": true,
  "minimumSalary": 0,
  "maximumSalary": 0,
  "minimumRating": 0,
  "maxListingPages": 5,
  "maxConcurrency": 1,
  "maxRequestRetries": 3,
  "minListingDelayMs": 700,
  "maxListingDelayMs": 2200
}
```

# Actor output Schema

## `jobListings` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("vjkhush/indeed-job-radar-actor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("vjkhush/indeed-job-radar-actor").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 '{}' |
apify call vjkhush/indeed-job-radar-actor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vjkhush/indeed-job-radar-actor"
        }
    }
}

```

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/UwYVE3ootB83mAWyX/builds/KEslwVm4gLfhUThTI/openapi.json