# Company Career-Page Jobs from Greenhouse, Lever and Ashby (`usta/ats-job-listings`) Actor

For recruiting-intelligence analysts and job aggregators: pull published jobs from public Greenhouse, Lever and Ashby career-page feeds as one row each, with title, department, location, remote flag, apply URL and description.

- **URL**: https://apify.com/usta/ats-job-listings.md
- **Developed by:** [US Tech Automations](https://apify.com/usta) (community)
- **Categories:** Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 result rows

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

## Company Career-Page Jobs from Greenhouse, Lever and Ashby

This actor pulls career site jobs from the public greenhouse jobs, lever jobs, and Ashby job listing api feeds as one published posting per row.

Paste a career-page URL or a board token. The board type is detected from the URL. Only the official public JSON feeds are read. The HTML career page is not scraped.

### Input

| Field | What it does |
|---|---|
| **Career-page URLs or board tokens** | `https://boards.greenhouse.io/stripe`, `https://jobs.lever.co/spotify`, `https://jobs.ashbyhq.com/ramp`, or `greenhouse:stripe` / `lever:spotify` / `ashby:ramp`. |
| **Keyword** | Optional. Keep jobs whose title, department, location or description contains this text. |
| **Location contains** | Optional. Keep jobs whose location field contains this text. |
| **Maximum rows** | Hard ceiling on rows returned, and therefore on the cost of the run. Default 50, maximum 10,000. |
| **Proxy configuration** | Optional Apify proxy. Off by default, including on a local run. |

### Pricing

**Pay per result. $0.003 per row. No start fee.**

Every dataset row bills from row one, including an error row for a board that 404s or is blocked. A run that returns no rows costs nothing. **Maximum rows** is the spend cap.

### Output (one row per job)

One example row from a real local run on 2026-09-20 against `https://boards.greenhouse.io/stripe` (description shortened here):

```json
{
  "error": false,
  "input_url": "https://boards.greenhouse.io/stripe",
  "source_url": "https://boards-api.greenhouse.io/v1/boards/stripe/jobs?content=true",
  "board_type": "greenhouse",
  "board_token": "stripe",
  "company": "Stripe",
  "job_id": "8172510",
  "title": "Abuse Investigator",
  "department": "8611 Security Analytics",
  "location": "Seattle, San Francisco, New York City",
  "remote": false,
  "employment_type": null,
  "posted_at": "2026-09-09T10:50:29-04:00",
  "updated_at": "2026-09-10T13:11:58-04:00",
  "apply_url": "https://stripe.com/jobs/search?gh_jid=8172510",
  "description": "Who we are About Stripe Stripe is a financial infrastructure platform for businesses. ...",
  "salary_range": null,
  "fetched_at": "2026-09-20T23:12:47Z"
}
```

| Field | What it holds |
|---|---|
| `company` | Greenhouse `company_name` when the feed publishes it; otherwise the board token |
| `board_type` | `greenhouse`, `lever`, or `ashby` |
| `title` | Job title |
| `department` | Department name when published |
| `location` | Primary location string when published |
| `remote` | `true` when the feed marks the job remote; `false` when it does not |
| `employment_type` | Lever commitment or Ashby employment type; Greenhouse Stripe jobs had none |
| `posted_at` / `updated_at` | Dates as published (`first_published` / `updated_at`, Lever `createdAt`, Ashby `publishedAt`) |
| `apply_url` | Public apply / hosted job URL |
| `description` | Job text with HTML stripped |
| `salary_range` | Range only when the feed publishes one (Ashby `includeCompensation`; Greenhouse/Lever structured salary fields). Stripe Greenhouse jobs had none, so this was `null`. |
| `error` | `true` only on a failed board URL (missing board, block, not JSON) |
| `fetched_at` | When this run read the feed, in UTC |

### What this does not do

- It does not log in, use cookies, solve a CAPTCHA, or read applicant data. These feeds do not contain applicants.
- It does not scrape career-page HTML. Only the three official JSON feeds above.
- It does not invent missing fields. Unreadable values are `null`.
- It does not guess a salary from job-description prose. If the feed has no salary field, `salary_range` is `null`.
- It does not discover which board a random company name uses. You paste the career URL or token.
- It does not grant a licence to republish a company's jobs. Each provider's terms still apply.
- It does not search Indeed, LinkedIn, or other job boards.

### Limits

- `maxItems` is 1–10,000 (default 50). The run stops there even if a board holds more jobs. Boards are read in the order you list them.
- Lever's robots.txt sets `Crawl-delay: 1`. This actor waits one second between HTTP calls.
- A 404 or block on one URL becomes one error row for that URL; other URLs in the same run still run.
- Email addresses and phone-number-shaped strings found in descriptions are replaced with `[redacted]`.

### Refunds and support

Refunds: if a run returns zero rows for a valid input, email operations@ustechautomations.com within 7 days and we refund that run. Support: same address, replies within 2 business days.

# Actor input Schema

## `startUrls` (type: `array`):

One or more public board URLs such as https://boards.greenhouse.io/stripe, https://jobs.lever.co/spotify, https://jobs.ashbyhq.com/ramp, or prefix tokens greenhouse:stripe / lever:spotify / ashby:ramp. The HTML career page is not scraped; only the official public JSON feed for that board is read.

## `keyword` (type: `string`):

Optional. Keep only jobs whose title, department, location or description contains this text (case-insensitive). Leave blank for every published job on the board.

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

Optional. Keep only jobs whose location field contains this text (case-insensitive), e.g. London or Remote.

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

Hard ceiling on rows returned, and therefore on the cost of the run. Every row bills at the listed price from row one; there is no start fee. A blocked or missing board produces one error row for that URL.

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

Optional Apify proxy. Leave off for a local run. Board feeds are ordinary HTTPS GET requests.

## Actor input object example

```json
{
  "startUrls": [
    "https://boards.greenhouse.io/stripe"
  ],
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

No description

## `csv` (type: `string`):

No description

## `report` (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 = {
    "startUrls": [
        "https://boards.greenhouse.io/stripe"
    ],
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("usta/ats-job-listings").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 = {
    "startUrls": ["https://boards.greenhouse.io/stripe"],
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("usta/ats-job-listings").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 '{
  "startUrls": [
    "https://boards.greenhouse.io/stripe"
  ],
  "maxItems": 50
}' |
apify call usta/ats-job-listings --silent --output-dataset

```

## MCP server setup

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

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/3M2t1mGeMLh0J7i5E/builds/lG0FLGPA6jiMr0DY1/openapi.json