# Career Site Jobs Scraper: Greenhouse, Lever, Ashby and More (`duytrinh98/career-site-jobs`) Actor

Collect public career board job postings from seven ATS platforms in one normalized dataset.

- **URL**: https://apify.com/duytrinh98/career-site-jobs.md
- **Developed by:** [Anh Duy Trịnh](https://apify.com/duytrinh98) (community)
- **Categories:** Jobs, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

## Career Site Jobs Scraper - 5 ATS Platforms

Get company career page job openings from **5 ATS platforms, from $3 per 1,000 jobs**. This career site jobs scraper combines ATS jobs API feeds for Greenhouse jobs, Lever jobs, Ashby jobs, Personio and Teamtailor into one dataset with salary, workplace and role filters, hiring signals and only-new mode for your job board aggregator. Give companies by name using a built-in directory of about 9,900 company boards on Greenhouse, Lever and Ashby, or scan a bounded directory page. It is an August 2026 snapshot, so some boards may have closed.

### What you get

Every record has all 30 fields below. Unknown values are null; no salary or date is invented. Raw employment types, countries and salary periods keep the source wording.

| Group | Field | Meaning |
| --- | --- | --- |
| Identity | ats | Source ATS; Lever EU uses lever-eu. |
| Identity | company | API display name, otherwise directory name for name/scan targets on Lever and Ashby, otherwise board slug. |
| Identity | companySlug | Resolved board identifier. |
| Identity | jobId | Source job ID as a string. |
| Identity | globalId | Stable ats:companySlug:jobId identity. |
| Identity | companyTotalJobs | Open postings found on the board before filters. |
| Role | title | Source job title. |
| Role | department | Department label. |
| Role | team | Team label. |
| Role | seniority | Explicit title-rule match, otherwise null. |
| Role | employmentType | Unchanged source employment label. |
| Role | employmentTypeNormalized | full_time, part_time, contract, internship, temporary, other; missing is null. |
| Location and workplace | location | Main location. |
| Location and workplace | locations | Distinct source locations, or null. |
| Location and workplace | country | Source country label or code. |
| Location and workplace | remote | true, false or null; hybrid is false. |
| Location and workplace | workplaceType | remote, hybrid, onsite or null. |
| Compensation | salaryMin | Structured numeric minimum. |
| Compensation | salaryMax | Structured numeric maximum. |
| Compensation | salaryCurrency | Source currency code. |
| Compensation | salaryPeriod | Source salary interval. |
| Compensation | salaryText | Source compensation text, including multiple ranges when supplied. |
| Dates | postedAt | ISO 8601 UTC posting date. |
| Dates | updatedAt | ISO 8601 UTC update date when available. |
| Dates | scrapedAt | ISO 8601 UTC collection time. |
| Links | url | Public listing URL. |
| Links | applyUrl | Application URL when supplied. |
| Links | sourceApi | Attribution: public API/feed URL used, for the board. |
| Text | descriptionText | Plain text, entities decoded, whitespace collapsed, contact strings redacted; capped at 20000 characters. |
| Text | descriptionHtml | Optional source description HTML with contact redaction; null by default. |

Seniority uses the first matching rule in this order: **c\_level > vp > director > manager > lead > principal > staff > senior > junior > entry > intern**. Rules recognize Chief X Officer or CEO/CTO/CFO/CIO/COO/CMO/CPO/CHRO/CISO; VP or Vice President; Director; Manager; Lead or Head of; Principal; Staff; Senior or Sr; Junior or Jr; Entry-level, Graduate or New Grad; Intern or Internship. Matching uses whole words. "Senior Manager" becomes manager, "Staff Engineer" becomes staff, and "Software Engineer" stays null. There is no default mid level.

Employment normalization maps explicit labels: Ashby FullTime, Lever Regular Full Time (Salary) and Personio permanent become full_time. Part-time, Contract, Intern/Internship and Temporary map to their corresponding categories. Unmapped labels, including Lever Remote, become other. Missing labels remain null; the supplied Greenhouse and Teamtailor feeds have no employment type.

### Use cases

- **Job board aggregator:** combine your selected company boards into a consistent feed.
- **Hiring signals for sales teams:** find matching openings by department, title and location.
- **Tracking competitor hiring:** schedule selected boards and save newly encountered postings.
- **Recruiting market maps:** compare roles, workplaces and source-provided compensation.
- **Job data for AI agents and RAG:** use stable IDs, plain descriptions and source links in retrieval pipelines.

### Quick start

1. Fill companies using any of three forms: company name ("Stripe"), URL ("https://jobs.lever.co/leverdemo"), or ats:slug ("ashby:ashby"). You can mix forms or keep the three default boards.
2. Choose optional filters and result limits, then click Start.
3. Open the Dataset to inspect results and export JSON or CSV. Open RUN-SUMMARY in the run's key-value store for board statuses.

### Supported ATS

| ATS | Accepted URL patterns | Explicit entry |
| --- | --- | --- |
| Greenhouse | boards.greenhouse.io/{token}, job-boards.greenhouse.io/{token}, boards.eu.greenhouse.io/{token}, job-boards.eu.greenhouse.io/{token}, boards-api.greenhouse.io/v1/boards/{token}, board embed URLs with ?for={token} | greenhouse:stripe |
| Lever | jobs.lever.co/{company} | lever:leverdemo |
| Lever EU | jobs.eu.lever.co/{company} | lever-eu:company |
| Ashby | jobs.ashbyhq.com/{company} | ashby:ashby |
| Personio | {company}.jobs.personio.de, {company}.jobs.personio.com | personio:personio |
| Teamtailor | {company}.teamtailor.com | teamtailor:career |

HTTP, HTTPS, www prefixes, trailing paths, and query strings are accepted. Slugs are case-normalized. Personio URLs retain their .de or .com domain; explicit Personio entries use .de. Duplicate ats:slug targets are fetched once. Custom domains and general company homepages are unsupported; use a supported ATS board URL. Unsupported entries produce a warning while other companies continue.

### Search by company name

Names are matched locally against the bundled directory, with no web search. Matching normalizes Unicode with NFKD, removes diacritics, lowercases, replaces & with "and", removes punctuation, collapses whitespace and repeatedly strips trailing legal suffixes: inc, incorporated, llc, ltd, limited, gmbh, ag, sa, sas, bv, plc, corp, corporation, co, company, pty, oy, ab, as, srl, spa and kk.

Resolution tries an exact normalized name, then an exact board slug (case-insensitive), then the normalized name with spaces removed. The first matching stage supplies all matching boards, capped at 3 per input name. There is no fuzzy guessing. An unresolved name is skipped without requests or charges, with up to 5 distinct prefix/substring name suggestions in the warning log and RUN-SUMMARY.unresolvedNames. Try a suggestion or supply a known board URL or ats:slug. Equal normalized names retain snapshot order for the 3-board cap.

### Scan the directory

Set directoryMaxCompanies to 1-500 to add directory boards. directoryAts chooses Greenhouse, Lever or Ashby (empty or absent means all three); directoryNameKeywords keeps names containing any normalized keyword; directoryOffset skips matching boards first. Selection filters, stably sorts by normalized name, then slices offset through offset + max. Equal normalized names retain snapshot order. The selected boards merge after companies entries and are deduplicated by ATS and slug. The cap and offset count company boards, so one company on multiple ATS can occupy multiple slots.

To scan 100 Ashby companies for remote engineering jobs:

```json
{
  "companies": [],
  "directoryAts": ["ashby"],
  "directoryNameKeywords": [],
  "directoryMaxCompanies": 100,
  "directoryOffset": 0,
  "titleKeywords": ["engineer", "engineering"],
  "remoteOnly": true,
  "maxJobs": 5000
}
```

Requests to one host are spaced 1 second apart, so checking 100 companies on one ATS takes about 2 minutes when responses are fast and no retries are needed. Save/charge limits can stop the run before all selected boards are checked. Increase directoryOffset to 100 for the next page with the same filters. directoryNameKeywords filters company names; titleKeywords and remoteOnly filter the fetched jobs. Set companies to \[] to scan alone in the input editor; programmatic input with directoryMaxCompanies > 0 and no companies also scans alone.

### Input

| Field | Type | Default | Behavior and example |
| --- | --- | --- | --- |
| companies | array | \["lever:leverdemo","ashby:ashby","personio:personio"] | Company names, supported board URLs or ats:slug entries; duplicate targets are fetched once. Example: \["Stripe","https://jobs.lever.co/leverdemo","ashby:ashby"]. |
| directoryAts | array | \[] | Directory ATS filter; empty means greenhouse, lever and ashby. Example: \["ashby"]. |
| directoryNameKeywords | array | \[] | Match any normalized company name keyword, before pagination. Example: \["labs"]. |
| directoryMaxCompanies | integer | 0 | Add up to 0-500 directory boards; 0 disables scanning. Example: 100. |
| directoryOffset | integer | 0 | Skip matching directory boards before taking the next page. Example: 100. |
| titleKeywords | array | unset | Keep titles containing any keyword, case-insensitive. Example: \["engineer"]. |
| locationKeywords | array | unset | Match any keyword across location, locations and country, case-insensitive. Example: \["Berlin"]. |
| remoteOnly | boolean | false | Require explicitly remote jobs; exclude hybrid and unknown. Example: true. |
| postedWithinDays | integer | unset | Keep jobs this many days old or newer; unknown dates pass. Example: 30. |
| maxJobsPerCompany | integer | 500 | Maximum saved jobs per company after filters. Example: 25. |
| maxJobs | integer | 100 | Maximum total saved jobs after filters (1-100000). Example: 100. |
| includeDescription | boolean | true | Save plain text up to 20000 characters. Example: true. |
| onlyNewJobs | boolean | false | Save only unseen IDs for the resolved board set using persistent history. Example: true. |
| excludeTitleKeywords | array | unset | Drop titles containing any keyword, case-insensitive. Example: \["intern"]. |
| employmentTypes | array | unset | Keep normalized types in this list; unknown types are dropped. Example: \["full_time"]. |
| departments | array | unset | Keep a match in department or team, case-insensitive. Example: \["engineering"]. |
| workplaceTypes | array | unset | Keep matching workplace types; unknown types are dropped. Example: \["remote","hybrid"]. |
| minSalary | integer | unset | Require salaryMax (fallback salaryMin) at least this number; unknown salaries are dropped; no currency conversion. Example: 100000. |
| includeDescriptionHtml | boolean | false | Include source description HTML with contact redaction; independent of plain text. Example: true. |

Provide companies entries or set directoryMaxCompanies > 0. With neither, the run warns clearly, makes no requests and exits with code 1. When both companies and scan are omitted programmatically, the same three default boards are used. With scan enabled and companies omitted, only scan targets are used. Arrays use case-insensitive substring OR matching for job keyword filters, and exact categories for employmentTypes and workplaceTypes. Empty filter arrays disable that filter. Separate categories combine with AND. Exclusions win over title inclusion. departments matches either department or team. Unknown employment and workplace types are dropped when their filters are set; other is a known normalized employment category. remoteOnly still requires remote=true, so combining it with hybrid returns no matches.

minSalary compares salaryMax, falling back to salaryMin only when salaryMax is null. Missing salary numbers are dropped when it is set. **No currency conversion or salary-period conversion is performed**: a salary floor compares the source numbers directly, so use boards with comparable currencies and periods. Unknown dates pass postedWithinDays. Filters precede save limits. maxJobs is 1-100000; maxJobsPerCompany, postedWithinDays and minSalary are integers of at least 1. Malformed fields warn and are ignored; an invalid companies array causes no boards to be fetched.

#### Example 1: quick run

```json
{
  "companies": ["Stripe", "https://jobs.lever.co/leverdemo", "ashby:ashby"],
  "maxJobs": 100
}
```

#### Example 2: remote senior engineering roles with a salary floor

```json
{
  "companies": ["ashby:ashby", "lever:leverdemo"],
  "titleKeywords": ["senior engineer", "senior software engineer", "staff engineer", "principal engineer"],
  "excludeTitleKeywords": ["intern", "junior"],
  "departments": ["engineering"],
  "employmentTypes": ["full_time"],
  "workplaceTypes": ["remote"],
  "minSalary": 150000,
  "includeDescriptionHtml": true,
  "maxJobsPerCompany": 25,
  "maxJobs": 50
}
```

This example can return zero if the boards have no matching openings. Title phrases select these roles; there is no seniority input filter. Compare currencies and salary periods before interpreting the floor.

#### Example 3: daily schedule with only new jobs

Create an Apify daily schedule using the same input and board set each day:

```json
{
  "companies": ["greenhouse:stripe", "ashby:ashby", "personio:personio"],
  "onlyNewJobs": true,
  "includeDescription": true,
  "maxJobsPerCompany": 500,
  "maxJobs": 5000
}
```

### Example output

This record comes from the supplied Lever fixture; scrapedAt illustrates the collection time.

```json
{
  "ats": "lever",
  "company": "leverdemo",
  "companySlug": "leverdemo",
  "jobId": "1dbf02a6-d434-4e47-8d66-3aba2c17bed1",
  "title": "Director of Diversity, Equity, and Inclusion",
  "department": "Executive",
  "team": "Executive",
  "location": "London, UK",
  "locations": [
    "London, UK"
  ],
  "country": "GB",
  "remote": false,
  "workplaceType": "onsite",
  "employmentType": "Regular Full Time (Salary)",
  "postedAt": "2024-06-17T14:17:57.107Z",
  "updatedAt": null,
  "url": "https://jobs.lever.co/leverdemo/1dbf02a6-d434-4e47-8d66-3aba2c17bed1",
  "applyUrl": "https://jobs.lever.co/leverdemo/1dbf02a6-d434-4e47-8d66-3aba2c17bed1/apply",
  "salaryMin": null,
  "salaryMax": null,
  "salaryCurrency": null,
  "salaryPeriod": null,
  "salaryText": null,
  "descriptionText": null,
  "sourceApi": "https://api.lever.co/v0/postings/leverdemo?mode=json",
  "scrapedAt": "2026-11-15T00:00:00.000Z",
  "globalId": "lever:leverdemo:1dbf02a6-d434-4e47-8d66-3aba2c17bed1",
  "seniority": "director",
  "employmentTypeNormalized": "full_time",
  "descriptionHtml": null,
  "companyTotalJobs": 4
}
```

Dates use Greenhouse first_published (fallback updated_at), Lever createdAt, Ashby publishedAt, Personio createdAt, and Teamtailor pubDate. Greenhouse supplies updatedAt when present. Greenhouse and Personio infer remote=true only from "remote" in location text; other locations remain unknown. Teamtailor remoteStatus=none maps to onsite/false. Lever and Ashby supply structured salaries. No salary values are extracted from prose. Lever/Ashby targets resolved from names or scans use the directory display name instead of a slug; API display names take precedence. URL/ats:slug-only runs keep their previous company values. The output schema and globalId format are unchanged.

includeDescriptionHtml is independent of includeDescription. Greenhouse escaped markup is decoded to real HTML first. Personio description sections and Lever description parts are combined in source order. HTML is source content and should be treated as untrusted markup by downstream applications.

### Only new jobs

Set onlyNewJobs=true to use the named key-value store career-site-jobs-state. Its state key is seen- plus SHA-1 of unique sorted resolved ats:slug strings joined by a newline. Input order and duplicate entries do not change history. Changing the board set creates separate history; changing filters does not. Personio .de and .com with the same slug share history; the first supplied domain is fetched.

The first run saves qualifying jobs; subsequent runs skip already saved IDs. Filtered jobs and jobs beyond limits are not marked seen. Content changes and closed jobs do not generate change records. At most 200000 IDs are retained, dropping the oldest. Disable onlyNewJobs to collect matching jobs without history. Avoid overlapping runs sharing the same board set: updates are not transactional, and a process failure after saving a job but before saving history can cause a repeat later.

### Run summary

RUN-SUMMARY contains startedAt, finishedAt, totals, companies and unsupported. Totals include companies (unique supported targets), found, saved, filteredOut, duplicates, alreadySeen and failedCompanies. Each company has input, ats, slug, resolvedFrom ("url", "ats:slug", "name" or "directory-scan"), status, found, saved, filteredOut and error. Unrecognized entries are retained in their original form. Vendors blocked by terms or robots rules appear as objects with input and reason and are never requested. Status is success, failed or skipped; an unreached board after a save/charge limit is skipped.

directory records source, snapshot and count for the bundled directory. resolvedFromDirectory counts unique targets with a directory name from name matching or scanning, before requests/save limits. unresolvedNames contains {input, suggestions} entries; these names also remain in unsupported for compatibility. directoryScan records selected, offset, maxCompanies and targets ({company, ats, slug}) before merging/deduplication. Overlaps retain the first supplied input and resolvedFrom; a directory name discovered on a duplicate is still available for display. A valid empty board appears as success with found=0; a closed board returning an HTTP error appears as failed with its error. An empty response alone cannot prove that a board has closed.

found counts parsed open postings on pages actually fetched, including repeated IDs. Filter, duplicate and already-seen counters count evaluated skips; jobs not evaluated after a limit are not included in those counters. Counts therefore need not sum to found. companyTotalJobs is the unfiltered board count from the parsed feed, even if saving stops early. Per-company log lines also report found, saved, skipped and why.

### Pricing

Pay per event **job**. There is **no start fee**, and **platform usage is included**.

| Apify plan | Per saved job | Per 1,000 saved jobs |
| --- | --- | --- |
| Free and Bronze | $0.004 | $4 |
| Silver | $0.0035 | $3.50 |
| Gold and higher | $0.003 | $3 |

Only saved jobs are charged. Filtered, duplicate and already-seen jobs cost nothing. Unsupported or failed boards do not trigger job events. A job is saved before its job event is charged; the Actor stops cleanly when the platform reports the event charge limit.

**Worked example:** 100 companies x 50 jobs = 5,000 saved jobs = **$20 on Free and Bronze**, or **$15 on Gold**. Filters and only-new mode reduce the number saved and charged.

### Data sources and fair use

Sources are public job-board endpoints that companies publish for candidates. No recruiter profiles or personal contact fields are collected. Creator/contact objects are excluded; email and common phone patterns and mailto/tel link labels are redacted from descriptions. Narrative descriptions may contain names that are not identified by the feed; pattern redaction is not a general personal-name recognizer. Do not use descriptions to build personal profiles.

There is no affiliation with any ATS vendor. Respect source terms, employer content rights and fair use. Requests use a descriptive User-Agent, at least 1000 ms between requests to one host, at most four company workers, a 30-second timeout, and up to two retries on 429 or 5xx after 2 and 6 seconds. Blocks and authentication are not bypassed.

### Company directory credit

The built-in directory is derived from the **ATS Company Directory by LastRound AI**, August 2026 snapshot, licensed [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Credit: [LastRound AI](https://lastroundai.com/blog/salary-transparency-study-2026). We converted the CSV to compact JSON, removed contact-like names and duplicate ATS/slug pairs, collapsed whitespace, sorted entries and normalized names for matching. See data/ATTRIBUTION.md for details. Personio and Teamtailor companies are not in the directory and must be given by URL or ats:slug.

### Limits

- Supported public boards only: no custom domains, browser rendering, authentication or historical archive. The name directory covers Greenhouse, Lever and Ashby only and is an August 2026 snapshot. Workday and other ATS platforms are unsupported in this version. Redirects are rejected; use canonical board URLs.
- Missing data stays null. Public feeds can lag employer changes. No currency conversion, annualization, inferred salary, geocoding or AI enrichment is performed.
- Plain descriptions are capped at 20000 characters. Optional HTML preserves source markup with the contact redaction above; it is not a guaranteed safe-to-render HTML document.
- Ashby unlisted jobs are excluded. Incomplete final RSS items are ignored.
- One failing board does not stop other boards. An empty valid feed or zero matching jobs is a successful result; no successful board fetch gives exit code 1. Dataset, charging or history-storage failures fail the run because safe completion cannot be confirmed.
- Global and company limits cap saved jobs. Near a global limit, response timing can determine which companies contribute. Directory scans add at most 500 boards per run; the cap does not restrict separately supplied companies. Jobs are fetched live for selected targets; there is no cached cross-company job index.

### FAQ

**How do I find a company's board URL?** First try its name for Greenhouse, Lever or Ashby. If unresolved, use a suggested name or open its careers page and follow the job-listing or application link. Look for a supported ATS domain in the table. Paste that board URL, or its ATS and board slug such as lever:leverdemo. General company homepages are not resolved.

**Is every company in the directory still hiring?** No. It is an August 2026 snapshot. Closed or empty boards are reported in RUN-SUMMARY and cost nothing; only saved jobs are charged. An empty board may be closed or simply have no current openings.

**Does a similar spelling resolve automatically?** No. Only exact normalized-name, exact slug or no-space-name matches resolve, with at most 3 boards per name. Prefix/substring suggestions require a new input; they are never fetched automatically.

**Are filtered or duplicate jobs charged?** No. Only jobs saved to the dataset trigger the job event. Already-seen IDs in only-new mode also cost nothing.

**Can I schedule daily runs?** Yes. Create an Apify schedule with your input and enable onlyNewJobs to skip IDs already saved for the same board set. Avoid overlapping runs sharing that history.

**Can I use the API or an AI agent?** Run the Actor through the Apify API and retrieve its dataset as JSON or CSV. AI agents can invoke the Actor through the Apify MCP server when configured with access to your account. No additional agent-specific input format is required.

**What happens when one board fails?** Its error is logged and included in RUN-SUMMARY. Other companies continue. If no board can be fetched successfully, the run exits with code 1.

**Does it support Workday or other ATS platforms?** They are not supported in this version. The supported list is limited to the five platforms above, with Lever EU as a regional variant.

**Why are SmartRecruiters, Breezy and Workday not supported?** Their terms or robots rules do not allow automated access, so the Actor does not call them.

**Why are there no results?** Check RUN-SUMMARY for failed or unsupported boards. A board can also be empty, all jobs can fail your filters, or only-new history can contain every qualifying ID. Unknown salaries or types are excluded when their corresponding filters are active.

**Are changed or closed jobs reported?** Only-new mode tracks saved identifiers. It does not emit edits, removals or closed-job events. Disable onlyNewJobs to collect the current matching postings again.

**Does the salary floor compare equivalent pay?** It compares source numbers directly, using salaryMax or salaryMin. Currencies and periods are not converted. Many boards supply no structured salary and are excluded by minSalary.

**Where can I report a problem?** Use the Actor's Issues tab with the board URL, run ID and relevant RUN-SUMMARY error. Avoid sharing personal data or credentials.

# Actor input Schema

## `companies` (type: `array`):

Company names, supported career board URLs or ats:slug entries; duplicates are fetched once; can be empty with directory scan enabled. Example: \["Stripe", "https://jobs.lever.co/leverdemo", "ashby:ashby"].

## `directoryAts` (type: `array`):

Take directory companies from these ATS platforms; empty means all three. Example: \["ashby"].

## `directoryNameKeywords` (type: `array`):

Keep directory company names containing any normalized keyword; empty disables this filter. Example: \["labs"].

## `directoryMaxCompanies` (type: `integer`):

Add up to this many directory boards, from 0 (off) to 500, before job filters and save limits. Example: 100.

## `directoryOffset` (type: `integer`):

Skip this many matching directory boards in normalized-name order before selecting the next page. Example: 100.

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

Keep titles containing any keyword, case-insensitive. Example: \["engineer"].

## `locationKeywords` (type: `array`):

Match any keyword across location, locations and country, case-insensitive. Example: \["Berlin"].

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

Require explicitly remote jobs; exclude hybrid and unknown. Example: true.

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

Keep jobs this many days old or newer; unknown dates pass. Example: 30.

## `maxJobsPerCompany` (type: `integer`):

Maximum saved jobs per company after filters. Example: 25.

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

Maximum total saved jobs after filters (1-100000). Example: 100.

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

Save plain text up to 20000 characters. Example: true.

## `onlyNewJobs` (type: `boolean`):

Save only unseen IDs for the resolved board set using persistent history. Example: true.

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

Drop titles containing any keyword, case-insensitive. Example: \["intern"].

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

Keep normalized types in this list; unknown types are dropped. Example: \["full_time"].

## `departments` (type: `array`):

Keep a match in department or team, case-insensitive. Example: \["engineering"].

## `workplaceTypes` (type: `array`):

Keep matching workplace types; unknown types are dropped. Example: \["remote","hybrid"].

## `minSalary` (type: `integer`):

Require salaryMax (fallback salaryMin) at least this number; unknown salaries are dropped; no currency conversion. Example: 100000.

## `includeDescriptionHtml` (type: `boolean`):

Include source description HTML with contact redaction; independent of plain text. Example: true.

## Actor input object example

```json
{
  "companies": [
    "lever:leverdemo",
    "ashby:ashby",
    "personio:personio"
  ],
  "directoryAts": [],
  "directoryNameKeywords": [],
  "directoryMaxCompanies": 0,
  "directoryOffset": 0,
  "remoteOnly": false,
  "maxJobsPerCompany": 500,
  "maxJobs": 100,
  "includeDescription": true,
  "onlyNewJobs": false,
  "includeDescriptionHtml": false
}
```

# Actor output Schema

## `jobs` (type: `string`):

Normalized public job board records.

# 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 = {
    "companies": [
        "lever:leverdemo",
        "ashby:ashby",
        "personio:personio"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("duytrinh98/career-site-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 = { "companies": [
        "lever:leverdemo",
        "ashby:ashby",
        "personio:personio",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("duytrinh98/career-site-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 '{
  "companies": [
    "lever:leverdemo",
    "ashby:ashby",
    "personio:personio"
  ]
}' |
apify call duytrinh98/career-site-jobs --silent --output-dataset

```

## MCP server setup

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