# Monitor jobs across Greenhouse, Lever, and Ashby

**Use case:** 

Collect current openings from a verified company watchlist across Greenhouse, Lever, and Ashby in one source-traceable dataset. Use stable job keys, locations, descriptions, apply links, timestamps, and raw source records to refresh a job board, talent product, or recruiting workflow.

## Input

```json
{
  "startUrls": [
    {
      "url": "https://jobs.ashbyhq.com/ashby",
      "userData": {
        "companyName": "Ashby"
      }
    },
    {
      "url": "https://job-boards.greenhouse.io/greenhouse",
      "userData": {
        "companyName": "Greenhouse"
      }
    },
    {
      "url": "https://jobs.lever.co/spotify",
      "userData": {
        "companyName": "Spotify"
      }
    }
  ],
  "includeGreenhouseDetails": false
}
```

## Output

```json
{
  "record_type": {
    "label": "Record type",
    "format": "string"
  },
  "notice_code": {
    "label": "Notice code",
    "format": "string"
  },
  "message": {
    "label": "Notice message",
    "format": "string"
  },
  "input_position": {
    "label": "Input position",
    "format": "integer"
  },
  "input_url": {
    "label": "Input job board URL",
    "format": "string"
  },
  "input_company_name": {
    "label": "Input company name",
    "format": "string"
  },
  "http_status": {
    "label": "HTTP status",
    "format": "integer"
  },
  "company": {
    "label": "Company",
    "format": "string"
  },
  "company_source": {
    "label": "Company name source",
    "format": "string"
  },
  "source": {
    "label": "ATS",
    "format": "string"
  },
  "region": {
    "label": "ATS region",
    "format": "string"
  },
  "board": {
    "label": "Job board identifier",
    "format": "string"
  },
  "title": {
    "label": "Job title",
    "format": "string"
  },
  "locations": {
    "label": "Locations",
    "format": "array"
  },
  "workplace_type": {
    "label": "Workplace type",
    "format": "string"
  },
  "employment_type": {
    "label": "Source employment type",
    "format": "string"
  },
  "source_published_at": {
    "label": "Source publication time",
    "format": "string"
  },
  "publication_time_kind": {
    "label": "Publication time meaning",
    "format": "string"
  },
  "apply_url": {
    "label": "Apply URL",
    "format": "string"
  },
  "job_key": {
    "label": "Job key",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Greenhouse, Lever & Ashby Job Scraper API Actor is ready to run with the inputs already set for "Monitor jobs across Greenhouse, Lever, and Ashby". [Sign up or log in](https://console.apify.com/create-task-from-example/sfN0KyE5L6xyxl6YR) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Monitor jobs across Greenhouse, Lever, and Ashby" task

The Greenhouse, Lever & Ashby Job Scraper API Actor will start running based on the input automatically. You can also change all the input fields, like verified company job board urls and include greenhouse salary details, to match your specific use case.

### 3. Receive the "Monitor jobs across Greenhouse, Lever, and Ashby" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as record type, notice code, notice message, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Monitor jobs across Greenhouse, Lever, and Ashby" task via API](https://apify.com/arjun_code/ats-job-scraper.md).

## About this Actor

This example demonstrates how to use [Greenhouse, Lever & Ashby Job Scraper API](https://apify.com/arjun_code/ats-job-scraper.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/arjun_code/ats-job-scraper.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/arjun_code/ats-job-scraper.md

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`).