# Jobs Feed: New Job Postings from 45k+ Career Sites, Daily (`jamie_developer/jobs-feed`) Actor

A bulk feed of new job postings for daily data pipelines: each run delivers the fresh jobs added since your last run to our index of 2M jobs from 49,000 company career sites on 19 ATSs, once, with no gaps. Filter by country, title, remote and ATS. For data warehouses, job boards and AI agents.

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

## Pricing

from $1.60 / 1,000 job in feeds

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

## Jobs Feed: Every New Job from 45k+ Company Career Sites, Daily

**A bulk feed of new job postings for data pipelines. Schedule it once a day and each run delivers every job that was added to our index of about 2 million jobs from 49,000 company career sites since your previous run: each job once, with no gaps, in one clean format.**

> **Why this one**
>
> - **Exactly once.** The feed keeps a position, like a bookmark. A run that stops at its job limit (or your cost limit) is picked up by the next run at the exact job where it stopped, so nothing is skipped and nothing arrives twice.
> - **Built for volume.** 100,000 jobs in a single run in about a minute, because runs read a ready-made daily index instead of crawling websites.
> - **Primary sources.** Jobs come from the employers' own applicant tracking systems (19 of them, from Greenhouse, Workday, Lever and Ashby to BambooHR, Paylocity, Personio and Teamtailor), with working apply links, not reposts from job boards.
> - **Simple filters** that keep a feed focused: countries, title keywords, remote/hybrid/on-site and ATS.

### How the feed works

1. **First run:** delivers the matching jobs whose posting date is in the last **N days** (default 1; 0 = every matching job in the index). Jobs on platforms that publish no posting date have no known age, so they are not part of the first run; the new ones arrive with later runs.
2. **Every later run:** delivers every matching job that was added to the index since the last job delivered before, in the order the jobs were added. The index is rebuilt once a day, so one run per day picks up each day's new jobs; schedule it in the morning (UTC).
   When the index starts reading a company's career site for the first time, that company's older openings are new to the index too. **Later runs: skip jobs posted more than N days ago** (default 14) leaves those out, so the feed carries fresh postings; the status message says how many were left out. Set it to 0 to receive them as well. Jobs without a posting date are always delivered.
3. **Max jobs per run** caps a run. Anything over the cap is queued, not lost: the status message says how many are waiting, and the next run starts with them.
4. The feed's position is stored per set of filters in a key-value store named `jobs-feed-state` in your account. Set a **Feed name** to keep the position when you change filters, or to run two feeds with the same filters.

On 31 October 2026 the index held 2,016,483 open jobs from 49,020 companies. A first run for jobs posted in the last day returned 17,062 jobs (10,850 in the United States).

### Filters

| Filter | What it does |
|---|---|
| **Countries** | `United States`, `Germany`, `GB`... from the ATS's country field or the location text (`Austin, TX` is US, `München` is DE) |
| **Job title contains any of** / **none of** | e.g. `engineer`, `nurse`, `sales`; exclude `intern`. Matches the start of words, case-insensitive. |
| **Workplace type** | remote, hybrid, on-site (on-site includes jobs with no stated type) |
| **Applicant tracking systems** | e.g. `greenhouse`, `smartrecruiters`; every run's SUMMARY lists the platforms in the current index |

Other filters of our Job Search API (salary, company, department, location text, employment type) are accepted through the API with the same field names.

#### Example input

All new US and Canadian jobs every day, starting with the last 3 days:

```json
{
  "countries": ["United States", "Canada"],
  "firstRunDays": 3,
  "maxJobs": 50000
}
```

### Output

One row per job, the same columns in every row (empty values are `null`): `title`, `company`, `ats`, `companySlug`, `jobId`, `location`, `locations`, `country`, `countryCode` (ISO 3166), `workplaceType`, `department`, `team`, `employmentType`, `postedAt`, `updatedAt`, `firstSeenAt` (when the job was added to the index: the feed's order), `lastSeenAt`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`, `salaryText`, `url`, `applyUrl`, `sourceUrl`, `scrapedAt`. `ats` + `companySlug` + `jobId` is a stable key for upserts.

```json
{
  "title": "Senior Software Engineer, Backend (AI Platform)",
  "company": "Affirm",
  "ats": "greenhouse",
  "companySlug": "affirm",
  "jobId": "8040386003",
  "location": "Remote US",
  "locations": ["Remote US"],
  "country": null,
  "countryCode": "US",
  "workplaceType": "remote",
  "department": "Infrastructure Platform Eng",
  "team": null,
  "employmentType": null,
  "postedAt": "2026-10-30T17:52:49Z",
  "updatedAt": "2026-10-30T21:15:12Z",
  "firstSeenAt": "2026-10-31T01:40:39Z",
  "lastSeenAt": "2026-10-31T01:53:41Z",
  "salaryMin": null,
  "salaryMax": null,
  "salaryCurrency": null,
  "salaryPeriod": null,
  "salaryText": null,
  "url": "https://job-boards.greenhouse.io/affirm/jobs/8040386003",
  "applyUrl": "https://job-boards.greenhouse.io/affirm/jobs/8040386003",
  "sourceUrl": "https://job-boards.greenhouse.io/affirm",
  "scrapedAt": "2026-10-31T06:15:51Z"
}
```

The run's **SUMMARY** record shows the feed's position, how many new jobs matched, how many were delivered and how many are queued, plus the index date and size.

### Plugging it into a pipeline

- **Schedule:** Apify Schedules, once a day.
- **Deliver:** integrations or a webhook on "run succeeded" push each run's dataset to Google Sheets, BigQuery, S3, Airtable, Make, Zapier or n8n, or fetch it from the dataset API as JSON, CSV or Excel.
- **Upsert:** key rows on `ats` + `companySlug` + `jobId`.
- **Need the full job ad?** The feed carries the index fields only, which keeps big runs fast. For the jobs you need, our **Job Search API** Actor fetches descriptions live (filter by company or job board).

### Use cases

- **Job boards and aggregators:** a daily stream of fresh, primary-source jobs for your country or niche.
- **AI agents and RAG:** a clean, deduplicated daily delta to embed instead of re-crawling.
- **Labour-market and hiring-signal analytics:** new openings per company, role, country and ATS, every day.
- **Recruitment marketing and sales intelligence:** which companies started hiring for which roles today.

### Pricing

You pay per job delivered plus a small fee per run; the exact prices are on the Pricing tab. Jobs your filters leave out and jobs delivered by earlier runs are never charged. **Max jobs per run** and the run's maximum cost both cap a run, and the queue keeps the rest for the next run.

### FAQ

**What counts as a new job?** A job that appeared in the index after the last job your feed delivered, unless its posting date is older than *Later runs: skip jobs posted more than N days ago* (14 days by default). A job seen again on the next day is not new. A job the employer reposts under a new id, or takes down and lists again later, arrives again.

**What if I miss a few days?** Nothing is lost. The next run delivers everything added since your last run (up to Max jobs; the rest follows in later runs).

**Can I change filters?** Yes. Without a feed name, new filters start a new feed (first-run rules apply). With a feed name, the position is kept and the new filters apply from there on.

**Is this legal?** The index is built only from the public job-board feeds that ATS vendors provide so companies can publish their openings. No logins, nothing bypassed, no candidate or personal data. The job ads belong to the employers. This Actor is not affiliated with any ATS vendor or with any employer in the results.

# Actor input Schema

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

Deliver only jobs in these countries. English names (United States, Germany, United Kingdom) or ISO codes (US, DE, GB). The country comes from the ATS when it gives one, otherwise from the location text; jobs whose country can't be determined, such as 'Remote' with no country, are left out when this is set. Leave empty for every country.

## `titleKeywords` (type: `array`):

Deliver only jobs whose title contains at least one of these keywords, e.g. engineer, nurse, sales. Case-insensitive; a keyword matches at the start of a word, so engineer also finds Engineering. Leave empty for all titles.

## `excludeTitleKeywords` (type: `array`):

Leave out jobs whose title contains any of these keywords, e.g. intern, senior. Same matching as above.

## `workplaceType` (type: `array`):

Deliver only remote, hybrid and/or on-site jobs. Most ATSs only flag remote and hybrid jobs, so On-site also includes jobs with no remote or hybrid indication. Leave empty for all.

## `ats` (type: `array`):

Deliver only jobs from these job board platforms, one per line. The index covers greenhouse, smartrecruiters, workday, lever, ashby, workable, teamtailor, paylocity, bamboohr, recruitee, softgarden, breezy, personio, rippling, jobvite, join, comeet, pinpoint and dvinci. Every run's SUMMARY record lists the platforms and job counts in the current index. Leave empty for all.

## `firstRunDays` (type: `integer`):

What the feed's first run delivers: the matching jobs whose posting date is in the last N days. Jobs without a posting date (some platforms publish none) start arriving with later runs. 0 = every matching job in the index. Later runs ignore this and deliver every job added to the index since the previous run.

## `maxAgeDays` (type: `integer`):

Later runs deliver jobs that are new to the index. When the index starts reading a company's career site for the first time, its older openings are new to the index too; this leaves out the ones whose posting date is more than N days old, so the feed carries fresh postings. Jobs without a posting date are always delivered. 0 = no limit.

## `feedName` (type: `string`):

The feed remembers which jobs it delivered, per set of filters. Leave empty to derive the name from the filters (changing a filter then starts a new feed); set a name to keep the position when you change filters, or to run two feeds with the same filters. Stored in a key-value store named jobs-feed-state in your account.

## `maxJobs` (type: `integer`):

Deliver at most this many jobs per run (up to 200,000). Jobs over the limit are not lost: the next run starts with them. You pay per job delivered, so this also caps the cost of a run.

## Actor input object example

```json
{
  "countries": [
    "United States",
    "Canada"
  ],
  "titleKeywords": [
    "engineer",
    "developer",
    "data"
  ],
  "excludeTitleKeywords": [
    "intern",
    "werkstudent"
  ],
  "workplaceType": [
    "remote"
  ],
  "ats": [
    "greenhouse",
    "lever",
    "ashby"
  ],
  "firstRunDays": 1,
  "maxAgeDays": 14,
  "maxJobs": 200
}
```

# Actor output Schema

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

The jobs this run delivered, in the order they were added to the index (dataset items).

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

Feed position, new jobs found, delivered and still queued, index date and size.

# 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 = {
    "countries": [
        "United States"
    ],
    "firstRunDays": 1,
    "maxJobs": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("jamie_developer/jobs-feed").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 = {
    "countries": ["United States"],
    "firstRunDays": 1,
    "maxJobs": 200,
}

# Run the Actor and wait for it to finish
run = client.actor("jamie_developer/jobs-feed").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 '{
  "countries": [
    "United States"
  ],
  "firstRunDays": 1,
  "maxJobs": 200
}' |
apify call jamie_developer/jobs-feed --silent --output-dataset

```

## MCP server setup

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

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/7KO3ctfvbxR9sEtOc/builds/v8fqeDV8Y8LiO0j9s/openapi.json