# Indeed Jobs Scraper - Full Description, Salary, 22 Countries (`lanternlab318/indeed-jobs`) Actor

Search Indeed by keyword, location and country site: full job description, salary text plus parsed min/max/period/currency, company rating, job types, remote flag, posting date. No login or cookies. Deduplicated across keywords and filters; incomplete rows are marked and free, never shown as empty.

- **URL**: https://apify.com/lanternlab318/indeed-jobs.md
- **Developed by:** [Lantern Lab](https://apify.com/lanternlab318) (community)
- **Stats:** 2 total users, 1 monthly users, 50.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.99 / 1,000 job postings

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?

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

## Indeed Jobs Scraper

Search Indeed by keyword, location and country site and get each job back with its **full description, salary text plus parsed min / max / period / currency, company name and rating, job types, remote or hybrid flag and posting date**. 22 Indeed country sites (US, UK, Canada, Australia, Germany, France, India and more). No Indeed login, no cookies of yours.

**Price:** $1.99 per 1,000 jobs. Partial job rows, keyword status rows and the run summary are free, and so is a keyword that finds nothing.

### Quick example

Input:

```json
{
  "keywords": ["nurse", "data analyst"],
  "location": "Texas",
  "country": "us",
  "maxItems": 100
}
```

One job row (`recordType: "job"`, shortened):

```json
{
  "recordType": "job",
  "jobKey": "c0942dff5a2b832c",
  "url": "https://www.indeed.com/viewjob?jk=c0942dff5a2b832c",
  "title": "Nurse (Ambulatory Care)",
  "companyName": "US Military Treatment Facilities under DHA",
  "companyRating": 2.3,
  "location": "El Paso, TX",
  "salaryText": "$98,624 - $125,249 a year",
  "salaryMin": 98624,
  "salaryMax": 125249,
  "salaryPeriod": "year",
  "currency": "USD",
  "jobTypes": ["Full-time"],
  "isRemote": false,
  "remoteType": null,
  "postedAt": "2026-10-23T05:00:00.000Z",
  "postedAtText": "1 day ago",
  "descriptionText": "Summary\n\nAbout the Position: This position is located at William Beaumont Army Medical Center, El Paso, Texas. ...",
  "country": "US",
  "keyword": "nurse",
  "searchLocation": "Texas",
  "site": "us",
  "matchedFilter": null,
  "partial": false,
  "collectedAt": "2026-10-24T17:51:43.120Z"
}
```

### Limits

- **Depth: about 100-250 distinct jobs per keyword and location.** Indeed shows a visitor who is not signed in only the **first page** of any search; asking for page 2 sends you to Indeed's sign-in page. This Actor does not sign in. To reach past page 1 it reads the first page of the same search under Indeed's own filters, one at a time (newest first, last 1/3/7/14 days, each job type, experience level, salary band, topic, wider radius...), and keeps only jobs it has not seen. Measured 2026-10-24: "nurse / Texas" reached 228 distinct jobs, "nurse / London" 119. For more jobs, add keywords or locations (e.g. several cities instead of one state). When a keyword ends below `maxItems` for this reason, its `query_status` row says `depthLimitReached: true`.
- **Salary is shown only when Indeed shows it**: the employer gave it, or Indeed read it out of the posting (`salarySource: "extraction"`). About 3 in 4 jobs in our tests. Missing salaries are `null`, never estimated.
- `companyRating` is `null` for employers without Indeed reviews; `jobTypes` is empty when Indeed shows no type.
- `postedAt` is the day Indeed lists as the posting date (midnight in the site's time zone, as an instant); `postedAtText` is what Indeed shows ("Just posted", "3 days ago").
- Public data only: no recruiter names, e-mails or phone numbers are collected as fields. The description is the employer's posting as Indeed publishes it.
- Runs a real Chrome browser on the Apify residential proxy in the site's country, because Indeed answers plain HTTP clients and datacenter IPs with a Cloudflare "Security Check" page. When Indeed refuses a request, the Actor waits, then retries from a fresh IP. If Indeed changes its bot check, rows may come back partial or refused; they are marked as such, never as "no results".
- When nothing matches, Indeed's "did not match any jobs" page sometimes still lists a few unrelated jobs; this Actor writes none of them and reports the keyword as `empty`.
- Indeed's firewall rejects some keywords outright (measured for one containing `<script>`). Such a keyword is written as `partial` with `partialReason: "query_rejected"` and is not retried; remove characters such as `<` and `>`. Ordinary punctuation (`C++ & "R&D"`) works.
- No scheduling or monitoring built in; use Apify schedules.

### What it does

1. For each keyword, reads page 1 of Indeed's search for that keyword, location and your filters (`datePosted`, `jobType`, `remoteOnly`).
2. If fewer than `maxItems` jobs were found and `expandWithFilters` is on, reads page 1 of the same search narrowed by one of the filters Indeed itself offers on that page, until `maxItems` jobs are written or 8 filtered pages in a row add nothing new.
3. Reads the full description of every new job: one request per page of jobs, not one per job.
4. Writes one row per job, deduplicated across all keywords and filters of the run.

### Input

| Field | Default | What it does |
| --- | --- | --- |
| `keywords` | - | Job titles, skills or companies, one per line. Repeats run once. |
| `location` | empty | City, state, region or postcode. Empty = whole country site. |
| `country` | `us` | Indeed site: `us`, `uk`, `ca`, `au`, `de`, `fr`, `in`, `ie`, `nz`, `sg`, `nl`, `es`, `it`, `at`, `ch`, `be`, `jp`, `br`, `mx`, `za`, `ae`, `pl`. |
| `datePosted` | `any` | `1`, `3`, `7` or `14` days. |
| `jobType` | `any` | `fulltime`, `parttime`, `contract`, `temporary`, `internship`, `permanent`. |
| `remoteOnly` | `false` | Only jobs Indeed tags as remote. |
| `includeDescription` | `true` | Full description per job. Off = Indeed's short snippet only. |
| `maxItems` | `100` | Max jobs per keyword (up to 1,000; see the depth limit above). |
| `expandWithFilters` | `true` | Reach past page 1 through Indeed's filters. Off = page 1 only (up to ~45 jobs on the US site, ~15 elsewhere). |
| `maxUpstreamRequests` | derived | Hard ceiling on requests to Indeed, retries included. |
| `proxyConfiguration` | residential | Apify residential proxy; the exit country follows `country`. |

### Output

Three kinds of rows, told apart by `recordType`:

- **`job`** - one per job. Main fields: `jobKey`, `url`, `title`, `companyName`, `companyRating`, `companyReviewCount`, `companyUrl`, `location`, `city`, `state`, `postalCode`, `country`, `salaryText`, `salaryMin`, `salaryMax`, `salaryPeriod` (`hour` / `day` / `week` / `month` / `year`), `currency`, `salarySource`, `jobTypes`, `isRemote`, `remoteType` (`remote` / `hybrid` / `null`), `postedAt` (= `publishedAt`), `postedAtText`, `descriptionText`, `descriptionHtml`, `snippet`, `sponsored`, `urgentlyHiring`, `easyApply`, plus the search that found it first (`keyword`, `searchLocation`, `site`, `matchedFilter`) and `collectedAt`. Charged.
  - `partial: true` with `partialReason` means the job was listed but its description could not be read in this run. **Not charged.**
- **`query_status`** - one per keyword: `outcome` (`found` / `empty` / `partial`), jobs written, repeated listings skipped, search pages and filters read, `depthLimitReached`, and a `statusText` that explains it in a sentence. Free.
- **`RUN_SUMMARY`** - the last row, also stored in the run's key-value store: totals, partial rows by reason, requests to Indeed, refusals and IP rotations, and why the run stopped if it stopped early. Free.

A keyword is `partial` (never `empty`) when Indeed refused requests, the request ceiling or your maximum charge was reached, or a page did not read as expected. A run that collected nothing because Indeed refused every request ends as **failed**, not as an empty success.

# Actor input Schema

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

Job titles, skills or companies to search for, one per line - what you would type into Indeed's "What" box. Repeated keywords (ignoring case) run once. A keyword that matches no job gets a status row that says so and is not charged.

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

City, state, region or postcode - Indeed's "Where" box. Leave empty to search the whole country site.

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

Which Indeed site to search. Each site lists that country's jobs, salaries in its currency, and is read from a residential IP in that country.

## `datePosted` (type: `string`):

Only jobs Indeed lists as posted within this many days.

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

Only jobs of this type. "Permanent" exists on the European sites.

## `remoteOnly` (type: `boolean`):

Only jobs Indeed tags as remote.

## `includeDescription` (type: `boolean`):

Read each job's full description (descriptionText and descriptionHtml). Costs one extra request per page of jobs, not per job. When off, rows carry Indeed's short snippet only.

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

Upper bound on the jobs collected for each keyword. Indeed shows a visitor who is not signed in only the first page of any search, so this Actor reaches further by reading the first page of the same search under Indeed's own filters (date, job type, experience, topic...). That typically gives 100-250 distinct jobs per keyword and location; a keyword can end below this number - see the README.

## `expandWithFilters` (type: `boolean`):

On: after the plain search, read the first page of the same search narrowed by one Indeed filter option at a time, until maxItems or until new filters add nothing. Off: the plain search's first page only (up to about 45 jobs on the US site, 15 elsewhere).

## `maxUpstreamRequests` (type: `integer`):

Hard ceiling on the requests this run sends to Indeed, retries included. At the ceiling collection stops - what was not reached is written with partialReason "upstream_request_cap" and the run then ends normally. Leave empty and the Actor works a ceiling out from your input, so a run is never unbounded.

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

The proxy the browser goes through. The default, Apify residential proxy in the site's country, is what this Actor is measured on; Indeed refuses datacenter IPs and requests without a proxy.

## Actor input object example

```json
{
  "keywords": [
    "nurse",
    "data analyst"
  ],
  "location": "Texas",
  "country": "us",
  "datePosted": "any",
  "jobType": "any",
  "remoteOnly": false,
  "includeDescription": true,
  "maxItems": 100,
  "expandWithFilters": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

No description

## `runSummary` (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 = {
    "keywords": [
        "nurse",
        "data analyst"
    ],
    "location": "Texas",
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("lanternlab318/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 = {
    "keywords": [
        "nurse",
        "data analyst",
    ],
    "location": "Texas",
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("lanternlab318/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 '{
  "keywords": [
    "nurse",
    "data analyst"
  ],
  "location": "Texas",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call lanternlab318/indeed-jobs --silent --output-dataset

```

## MCP server setup

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