# Employer-Direct Jobs API - 2M+ Live Listings (JOA) (`job_opportunities_api/job-opportunities-api`) Actor

Search live and closed job listings taken straight from employer ATS, career sites and public agencies. Every field tagged published or inferred, with freshness timestamps. No scraping, no proxies - pay per record.

- **URL**: https://apify.com/job\_opportunities\_api/job-opportunities-api.md
- **Developed by:** [Loukas Tzekos](https://apify.com/job_opportunities_api) (community)
- **Categories:** Jobs, Lead generation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## Employer-Direct Jobs API — Job Opportunities API (JOA) on Apify

Search **live and closed job listings taken straight from the source**: employer applicant-tracking systems, company career pages and public employment agencies. More than **2 million live listings worldwide**, of which **466,000+ employer-direct listings in Europe** — with **every field labelled `published` or `inferred`** so you know what the employer said and what we guessed.

This Actor is the Apify edition of [jobopportunitiesapi.org](https://jobopportunitiesapi.org). No scraping happens at run time: it reads a continuously refreshed ledger, so runs are **fast, stable and cheap** — no proxies, no blocked requests, no broken selectors.

### What you can pull

| Mode | What it returns | Typical use |
|---|---|---|
| **Jobs** | Live vacancies, newest first | Job boards, AI job agents, lead lists, market research |
| **Closed jobs** | Roles that left their source, with `closed_at` and `closed_reason` | Hiring-signal data: how fast do employers fill roles? |
| **Companies** | Employers with open roles, industry, org type, website, open-role counts | Sales prospecting, employer databases |

#### Why this data is different

- **Per-field provenance.** `field_sources` marks each field `published`, `inferred` or `absent`. Filter to source-confirmed remote status only.
- **Freshness you can query.** `last_verified_at` is when we last re-confirmed the vacancy at its source — about 97% of the ledger is re-checked inside 48 hours. Filter with *Re-verified within (days)*.
- **Closure history.** Roles that came off their source are kept, with the reason.
- **Every row links to the employer's own apply page** (`apply_url`) and to a public JOA page (`joa_url`).
- **Redistribution is enforced by a database join**, not a filter someone can forget: only employer ATS, career-site and government-agency sources are served.

#### Honest coverage notes

- Salary is published by the employer on roughly **2%** of rows. Use *Only rows with a published salary* together with a country.
- **Remote / hybrid / on-site** is inferred for most rows; tick *Only source-confirmed remote status* if you need certainty.
- Seniority and category are inferred and shown only when confidence is high; otherwise they are absent, never guessed.

### Pricing — pay only for records returned

| Event | Price | Per 1,000 |
|---|---|---|
| Job listing returned | **$0.002** | $2.00 |
| Closed job returned | **$0.004** | $4.00 |
| Employer returned | **$0.002** | $2.00 |
| Actor start | $0.00005 | — |

Empty pages and searches that match nothing cost nothing beyond the start fee. Set **Max results** and Apify's **maximum cost per run** to cap spend; the run stops the moment either is reached. The Apify free plan's monthly credit covers roughly 2,500 job listings.

### Input

Every field is optional; the defaults return 100 recent jobs.

```json
{
  "mode": "jobs",
  "query": "data engineer",
  "countries": ["DE", "NL"],
  "remote": ["remote", "hybrid"],
  "seniorities": ["Senior", "Lead"],
  "verifiedWithinDays": 2,
  "postedWithinDays": 14,
  "includeDescription": false,
  "maxResults": 500
}
```

Filters cover: full-text query, title include/exclude, description text, countries, city, work model, employment type, seniority, job category, source type, company slugs, company domains, published salary and minimum annual salary (EUR), posted / re-verified / closed windows, and full advert text.

#### Pulling a large set in several runs

Each run writes a `SUMMARY` record to the key-value store containing `next_cursor` when more results exist. Paste it into **Start cursor** (keep the other inputs identical) to continue exactly where the previous run stopped.

### Output (Jobs mode, abridged)

```json
{
  "id": "fdf6503a-df64-493b-9a50-eaef5e2a11f0",
  "title": "Spezialist Direktvermarktung und Partnerbetreuung (m/w/d)",
  "company": "E.VITA GmbH",
  "country": "DE",
  "city": "Stuttgart",
  "remote": "hybrid",
  "remote_inferred": true,
  "employment_type": "Full-time",
  "salary_min": 49000,
  "salary_max": 65000,
  "salary_currency": "EUR",
  "salary_period": "year",
  "posted_at": "2026-09-28T00:00:00Z",
  "last_verified_at": "2026-09-29T09:05:30Z",
  "apply_url": "https://evita-energie.softgarden.io/job/67688737/",
  "source_type": "career_site",
  "field_sources": { "remote": "inferred", "salary": "published", "location": "published" },
  "joa_url": "https://jobopportunitiesapi.org/job/spezialist-direktvermarktung-und-partnerbetreuung-m-w-d-fdf6503a"
}
```

Download as JSON, CSV, Excel, XML or HTML, or read it through the Apify API and integrations (Make, Zapier, n8n, Google Sheets, webhooks, MCP for AI agents).

### FAQ

**Is this scraping LinkedIn or Indeed?** No. Those aggregators are excluded on purpose. Listings come from employer ATS platforms (Greenhouse, Lever, Workday, SmartRecruiters and many more), company career pages and public agencies.

**How fresh is it?** The ledger refreshes every few hours; each row carries `last_verified_at`.

**Can I integrate directly instead?** Yes — the same data is available as a REST API with a free tier at [jobopportunitiesapi.org](https://jobopportunitiesapi.org), and per call on [API.market](https://api.market/store/tzekos/jobopportunitiesapi). This Actor is the pay-per-result option inside Apify.

**A run failed with a credential message.** That is an operator-side problem, never your input. Please open an issue on the Actor's Issues tab.

### Support

Issues and feature requests: the Actor's **Issues** tab or [GitHub](https://github.com/lucagiftzek/JOA-Apify/issues). Built and operated by [TZEKOS.EU](https://tzekos.eu).

# Actor input Schema

## `mode` (type: `string`):

What to fetch. Jobs = live vacancies. Closed jobs = roles that left their source (hiring signal). Companies = employers with open roles.

## `maxResults` (type: `integer`):

Hard cap on records returned (and billed). The run stops as soon as it is reached. Use Start cursor to continue a large pull in a later run.

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

Full-text over job title, company name and location (Jobs / Closed jobs), or over the company name (Companies). Example: data engineer berlin

## `titleQuery` (type: `string`):

Full-text over the job title only. ANDs with everything else. Jobs / Closed jobs only.

## `titleExclude` (type: `string`):

Drop rows whose title matches these words, e.g. intern trainee. Jobs / Closed jobs only.

## `descriptionContains` (type: `string`):

Full-text over the advert body (only rows that carry a description). Example: kubernetes terraform. Jobs / Closed jobs only.

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

ISO-3166 alpha-2 codes, e.g. DE, GR, FR, NL. Empty = worldwide.

## `excludeCountries` (type: `array`):

ISO-3166 alpha-2 codes to remove.

## `city` (type: `string`):

City name as it appears in the ledger, e.g. Berlin. Jobs / Closed jobs only.

## `remote` (type: `array`):

Remote / hybrid / on-site. Note: for most rows the work model is INFERRED — tick 'Only source-confirmed remote status' to keep rows where the employer stated it.

## `remoteConfirmed` (type: `boolean`):

Keep only rows whose remote status was published by the employer (not inferred by us).

## `employmentTypes` (type: `array`):

Full-time, Part-time, Contract, Temporary, Internship, or not\_stated.

## `seniorities` (type: `array`):

Entry, Intern, Mid, Senior, Lead, Manager, Director, Executive, or not\_stated. Seniority is inferred and only stated where confidence is high.

## `categories` (type: `array`):

Job family. 'uncategorised' selects rows without a confident classification.

## `sourceTypes` (type: `array`):

Where the row comes from: Employer ATS, company career site, or public employment agency.

## `companySlugs` (type: `array`):

Restrict to specific employers by JOA slug (find slugs in Companies mode), e.g. e-vita-gmbh.

## `companyDomains` (type: `array`):

Restrict to employers by bare domain (no scheme, no path), e.g. stripe.com, figma.com.

## `hasSalary` (type: `boolean`):

Keep only rows whose salary was published by the employer. Roughly 2% of the ledger carries structured salary — combine with a country to keep results useful.

## `minSalaryEurAnnual` (type: `integer`):

Lower bound on the normalised annual salary in EUR. Implies published salary.

## `postedWithinDays` (type: `integer`):

Only roles posted in the last N days. Jobs / Closed jobs only.

## `verifiedWithinDays` (type: `integer`):

Only roles re-confirmed at their source in the last N days — the freshness filter. 97% of the ledger is re-checked inside 48 hours, so 2 is a good value. Jobs / Closed jobs only.

## `closedWithinDays` (type: `integer`):

Closed jobs mode: only roles that closed in the last N days.

## `closedReason` (type: `string`):

Closed jobs mode: why the role left the ledger.

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

Add the full job description (about 2.5 KB per row) in a description field. Same price per record.

## `companyOrgType` (type: `string`):

Companies mode only: organisation type filter, e.g. BPO, Staffing, Enterprise (see the values in Companies-mode output).

## `companyHasWebsite` (type: `boolean`):

Companies mode only.

## `startCursor` (type: `string`):

Resume a previous pull: paste the next\_cursor from that run's SUMMARY record. Keep every other input identical.

## Actor input object example

```json
{
  "mode": "jobs",
  "maxResults": 100,
  "query": "software engineer",
  "countries": [
    "DE"
  ],
  "remoteConfirmed": false,
  "hasSalary": false,
  "closedReason": "",
  "includeDescription": false,
  "companyHasWebsite": false
}
```

# Actor output Schema

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

Job listings, closed jobs or employers (depending on the mode), as a table you can download as JSON, CSV or Excel.

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

Records returned, why the run stopped, the applied filters and next\_cursor for resuming.

# 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 = {
    "maxResults": 100,
    "query": "software engineer",
    "countries": [
        "DE"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("job_opportunities_api/job-opportunities-api").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 = {
    "maxResults": 100,
    "query": "software engineer",
    "countries": ["DE"],
}

# Run the Actor and wait for it to finish
run = client.actor("job_opportunities_api/job-opportunities-api").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 '{
  "maxResults": 100,
  "query": "software engineer",
  "countries": [
    "DE"
  ]
}' |
apify call job_opportunities_api/job-opportunities-api --silent --output-dataset

```

## MCP server setup

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

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/rmycjHKmkZl19lQWH/builds/WNLqtTkPYCPmPrTCL/openapi.json