# Jobs With Salary: Pay-Transparent Job Listings API (`variegated_trifle/jobs-with-salary`) Actor

Search live job postings that publish a salary range, from the career pages of thousands of companies. Filter by pay, role, location, remote and freshness.

- **URL**: https://apify.com/variegated_trifle/jobs-with-salary.md
- **Developed by:** [John Veil](https://apify.com/variegated_trifle) (community)
- **Categories:** Jobs, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 job returneds

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

## Jobs With Salary

Search live job postings that **publish a pay range**. Every result has a salary, so there is nothing to
filter out and nothing to guess. Postings come from the public career pages of companies hosted on
Greenhouse, Lever and Ashby, refreshed on a schedule.

### What you can do with it

- Build a pay-transparent job board or newsletter ("remote engineering jobs paying $150k+")
- Benchmark compensation by role, company or location
- Feed a job-matching or career-coaching tool with real pay data
- Watch for new high-paying jobs: run it on a schedule with **Newly discovered within (hours)** set

### Input

| Field | What it does |
| --- | --- |
| Job title keywords | Matches title, department or team (any word) |
| Exclude title keywords | Drops titles containing these |
| Minimum / maximum yearly salary | Compared as a **yearly** figure. Hourly, weekly and monthly pay is converted first |
| Currency | One currency, or ANY. **No exchange-rate conversion is applied** |
| Remote only | Workplace type is remote. When a posting states no workplace type, the title or a location saying remote counts. Hybrid and on-site postings are excluded |
| Location contains | Any of the given texts |
| Companies | Company name or board slug |
| Employment types | Exact match, case-insensitive; not every posting states one |
| Job board source | Greenhouse, Lever, Ashby |
| Posted within (days) | Uses the posting date, or the date we first saw it |
| Newly discovered within (hours) | Only jobs first seen recently; use on a schedule |
| Sort by | Newest, highest pay, lowest pay. Pay is ranked by the middle of the yearly range |
| Maximum results | Also your cost cap |

### Output

One item per job: `title`, `company`, `url`, `applyUrl`, `locations`, `remote`, `employmentType`,
`department`, `team`, `salary {min, max, currency, interval}`, `annualMin`, `annualMax`,
`postedAt`, `firstSeenAt`, `snippet` (first part of the description), `ats`.

### Example output

One result (shortened). Every record carries a real pay range and its yearly equivalent.

```json
{
  "title": "Senior Inside Sales Advisor (Remote/Eastern Time)",
  "company": "A Place for Mom",
  "ats": "ashby",
  "url": "https://jobs.ashbyhq.com/a-place-for-mom/026a6fa8-f304-4c30-a470-948e37f7fdc2",
  "locations": ["Raleigh, NC", "Spartanburg, SC", "Newport, RI"],
  "remote": "remote",
  "employmentType": "FullTime",
  "department": "Sales",
  "salary": { "min": 86500, "max": 86500, "currency": "USD", "interval": "year" },
  "annualMin": 86500,
  "annualMax": 86500,
  "postedAt": "2026-09-16T20:13:23.767Z",
  "firstSeenAt": "2026-10-12T12:51:54.683Z",
  "snippet": "As a Senior Inside Sales Consultant, you will work with families who have already begun their search…"
}
```

### Example inputs

**Remote engineering jobs paying $150k or more, best paid first**

```json
{ "keywords": ["engineer"], "remoteOnly": true, "minSalary": 150000, "currency": "USD", "sortBy": "salaryDesc", "maxItems": 100 }
```

**Only jobs discovered in the last 24 hours (run this on a daily schedule)**

```json
{ "firstSeenWithinHours": 24, "currency": "USD", "maxItems": 500 }
```

**Data roles in London, any pay**

```json
{ "keywords": ["data scientist", "data engineer", "analytics"], "locationContains": ["london"], "maxItems": 200 }
```

### Pricing

You pay per job returned. Set **Maximum results** and the platform's maximum cost per run to cap spend.

### Good to know

- **Pay period:** some boards omit whether a figure is hourly or yearly. We infer it only when the amount makes it obvious (for example under 500 is hourly, over 20,000 is yearly in USD, EUR, GBP, CAD or AUD). When unsure the period is `null`, and those jobs are skipped by salary filters.
- **Data cleaning:** a pay period that is impossible for its label but plausible as yearly (for example $210,000 per month) is treated as yearly and flagged `adjusted`. Ranges wider than 5x and filler numbers such as 1111111 are dropped.
- **Several pay ranges:** a posting can list one range per country or pay zone. `salary` is the first listed.
- **Coverage:** companies that use Greenhouse, Lever or Ashby. Workday, iCIMS, SuccessFactors and others are not included.
- **First-seen dates** start from our first sighting, so "newly discovered" is only meaningful after the second refresh.
- **Source:** public job-board APIs that companies publish for this purpose. No logins, no personal data.

# Actor input Schema

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

Match jobs whose title, department or team contains ANY of these words (e.g. backend, data scientist).

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these (e.g. intern, manager).

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

Keep jobs whose top of range, converted to a yearly figure, reaches this amount. Hourly, weekly and monthly pay is converted to yearly. Jobs with an unknown pay period are skipped when this is set. Amounts are in the job's own currency, so combine with Currency.

## `maxSalary` (type: `integer`):

Keep jobs whose bottom of range, converted to a yearly figure, is at or below this amount. 0 means no limit.

## `currency` (type: `string`):

Only jobs paid in this currency. ANY keeps all currencies; no exchange-rate conversion is applied.

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

Only remote jobs (the posting says remote in its workplace type, title or location).

## `locationContains` (type: `array`):

Match jobs with a location containing ANY of these texts (e.g. germany, london, new york).

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

Only these companies. Use the company name or its board slug (the part after the job-board domain).

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

Match the posting's employment type exactly, case-insensitive (e.g. FullTime, Full-time, Contract). Not every posting states one.

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

Restrict to postings from these job boards. Leave empty for all.

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

Only jobs posted in the last N days. 0 means any age. When a posting has no posted date, the date we first saw it is used.

## `firstSeenWithinHours` (type: `integer`):

Only jobs we first saw in the last N hours. Use this on a schedule to get just the new jobs since your last run.

## `sortBy` (type: `string`):

Order of the results: newest first, highest pay first, or lowest pay first. Pay is ranked by the middle of the yearly range, so one very wide range cannot outrank a solid one.

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

You are charged per result returned, so this is also your cost cap.

## Actor input object example

```json
{
  "keywords": [
    "engineer"
  ],
  "minSalary": 0,
  "maxSalary": 0,
  "currency": "ANY",
  "remoteOnly": false,
  "postedWithinDays": 0,
  "firstSeenWithinHours": 0,
  "sortBy": "newest",
  "maxItems": 100
}
```

# Actor output Schema

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

Matching job postings that publish a salary range, one item per job.

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

How many jobs were scanned, how many matched, how many were returned, and when the data was generated.

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

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

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

```

## MCP server setup

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

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/Bsx9waymfcgcd5CNd/builds/s5hvNbb604jOoG7ra/openapi.json