# Indeed Job Listings Scraper (`usestring/indeed-jobs`) Actor

Collect job postings from Indeed search results by query and location.

- **URL**: https://apify.com/usestring/indeed-jobs.md
- **Developed by:** [String](https://apify.com/usestring) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 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/platform/actors/running/actors-in-store#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 Scraper — titles, companies, salaries

The Indeed Job Scraper collects job postings from Indeed search results. Give it search terms and a
location, and it returns Indeed's own result set for each search: job title, company, location, the
posting's stated salary, employer rating and posting date.

To scrape Indeed job listings, put one or more search terms in `queries`, optionally a `location`,
and pick a `country` — `us`, `uk`, `ca`, `au` or `de`. No Indeed account, login or cookies are used;
this Actor reads what a logged-out visitor sees. Around **39 jobs per search**, across five
countries.

### What it returns

| Field | Type | Notes |
| --- | --- | --- |
| `jobKey` | string | Indeed's own job ID — stable, use it to de-duplicate |
| `title` | string | |
| `company` | string | |
| `location` | string | Includes the postcode where Indeed shows one |
| `salary` | string | The posting's stated pay, e.g. `"$120,000 - $140,000 a year"` — `null` when the posting does not state one |
| `companyRating` | number | Indeed employer rating out of 5 |
| `companyReviewCount` | number | |
| `postedAt` | string | ISO 8601 timestamp |
| `jobUrl` | string | Direct link to the posting |
| `query`, `country`, `searchLocation`, `sourceUrl`, `collectedAt` | string | Provenance for every row |

### Input

```json
{ "queries": ["software engineer", "data analyst"], "location": "Austin, TX", "country": "us" }
```

| Field | Description |
| --- | --- |
| `queries` | Search terms. Required, up to 50. Duplicates collapse to one fetch. |
| `location` | Optional location filter, e.g. `"Austin, TX"`. |
| `country` | `us` (default), `uk`, `ca`, `au` or `de`. |
| `maxItems` | Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below. |
| `concurrency` | Searches run in parallel. Default 3. |

### Use cases

- Talent-market and compensation research across roles and cities
- Competitor hiring signals — who is growing which team
- Filling an ATS or job board with live Indeed postings
- Recruiting lead lists by role, employer or location
- Tracking Indeed postings over time by re-running on a schedule

### Reliability

Measured across 30 distinct Indeed job searches in one run: **29/30 searches succeeded, 1,132 jobs
collected**, every schema field populated.

The `salary` field is the Indeed posting's own stated pay. It is deliberately not inferred from
Indeed's estimated-salary panel, which sits beside the results and describes the market rather than
the job — so `salary` is `null` when the employer did not state one, rather than confidently wrong.

An Indeed search that cannot be read is recorded in the run's `SUMMARY` under `failures`, and a run
where every search failed exits with an error.

### Frequently asked questions

**Do I need an Indeed account or API key?** No. The Indeed Job Scraper uses no account, login,
cookies or API key — only public Indeed search pages are read.

**Which countries does the Indeed Job Scraper support?** Five: United States (`us`), United Kingdom
(`uk`), Canada (`ca`), Australia (`au`) and Germany (`de`), selected with the `country` field. One
run searches one country.

**Is the Indeed salary real or estimated?** Real — `salary` is the posting's stated pay, and `null`
when the posting gives none. Indeed's own salary estimate is never substituted.

**How many Indeed jobs does one search return?** Around 39, which is what one Indeed results page
carries. Ten search terms therefore return roughly 390 jobs.

**How do I de-duplicate Indeed jobs across runs?** Use `jobKey`, Indeed's stable job identifier,
which does not change between runs for the same posting.

**Can I get the full Indeed job description?** No. This Actor returns the fields Indeed exposes on
the search results page; it does not open each posting. Follow `jobUrl` for the full description.

**What happens on a free Apify plan?** The run stops at 250 requests and 250 results and reports
that it hit the limit. Any paid plan runs the full input.

### Limitations

The Indeed Job Scraper reads one results page per search, so it collects the first page rather than
paginating a whole market; run several narrower queries to widen coverage. Full job descriptions,
application counts and recruiter contacts are out of scope.

### Free plan limit

Runs started from an Apify **free plan** stop at **250 requests and 250 results**, and the run
reports that it reached the limit. Any paid plan runs the full input and `maxItems` you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not
cover for free-plan runs. It binds on requests as well as results so that a large input list cannot
spend those fetches for rows the run will not return.

# Actor input Schema

## `queries` (type: `array`):

Job search terms, e.g. "software engineer".

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

Optional location filter.

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

Indeed domain: us, uk, ca, au or de.

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

Global cap on dataset items. Runs started from an Apify free plan stop at 250 requests and 250 results; any paid plan runs the full amount.

## `concurrency` (type: `integer`):

Targets fetched in parallel.

## Actor input object example

```json
{
  "queries": [
    "software engineer"
  ],
  "country": "us",
  "maxItems": 1000,
  "concurrency": 3
}
```

# Actor output Schema

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

Collect job postings from Indeed search results by query and location.

## `summary` (type: `string`):

Item count, failure count and every target that failed, with its error.

# 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 = {
    "queries": [
        "software engineer"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("usestring/indeed-jobs").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 = { "queries": ["software engineer"] }

# Run the Actor and wait for it to finish
run = client.actor("usestring/indeed-jobs").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 '{
  "queries": [
    "software engineer"
  ]
}' |
apify call usestring/indeed-jobs --silent --output-dataset

```

## MCP server setup

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

```

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/ywZYtSaoq9Exxkifs/builds/oGOZqivLHcyWugtsg/openapi.json