# Greenhouse Job Keyword Evidence Report (`ecomopskits/greenhouse-job-keyword-evidence`) Actor

Scan one public Greenhouse job board for literal keywords in titles and descriptions. Get source links and evidence excerpts in one JSON report. USD0.01 per completed board, including zero matches. No inferred buying intent.

- **URL**: https://apify.com/ecomopskits/greenhouse-job-keyword-evidence.md
- **Developed by:** [Vladimir Oprea](https://apify.com/ecomopskits) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 complete greenhouse keyword reports

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

## Greenhouse Job Keyword Evidence Report

Find jobs mentioning your chosen technologies or phrases on one public Greenhouse
company board. Get a JSON report with the job title, location, source link and a
short text excerpt for each matched keyword. Useful for agencies and researchers
checking a known company's job descriptions without reading every posting.

This is a literal text scan, not a prediction of purchase intent or a verified
technology installation. A mention may be a requirement, a comparison or a
negated statement. Read the excerpt and original job before drawing conclusions.

### Run a scan

Enter a board slug from a public Greenhouse careers URL and 1–10 keywords:

```json
{"boardToken":"figma","keywords":["Salesforce","Snowflake"]}
```

Use the company's Greenhouse board slug, which can differ from its company name.
For a URL ending in `/figma`, the slug is `figma`. URLs themselves are not accepted.
The Actor reads the public Greenhouse Job Board API once. No login, browser,
proxy, application submission or employer discovery is involved.

Matching is case-insensitive literal text with word boundaries: `Java` does not
match `JavaScript`. Phrases match normalized whitespace; punctuation must match.
Any supplied keyword can qualify a job. Each keyword has at most one excerpt per
job, preferring its first title match, otherwise its first description match.
HTML is converted to text. There is no stemming, synonym expansion, semantic
classification, salary extraction, contact enrichment or cross-run history.

### Output and price

One completed board scan costs **USD0.01**, including a scan with **zero matches**
or an empty board. Platform run usage is included. There is no start charge and
no per-job charge. Invalid input, source failures, exceeded limits or insufficient
event budget create no report and no custom charge. Apify storage or export
charges after the run can be separate under your platform plan.

The default Dataset contains one nested JSON report. Use JSON for the complete
`matches` and `evidence` arrays; this is not a flat spreadsheet export. `SUMMARY`
records completion, counts or the failure reason. The output links expose both.

Example **synthetic** match from a one-job source:

```json
{
  "boardToken": "example-company",
  "jobsScanned": 1,
  "matchingJobs": 1,
  "keywords": ["Salesforce"],
  "scanComplete": true,
  "matches": [{
    "jobId": 123,
    "title": "Business Systems Engineer",
    "location": "Remote",
    "jobUrl": "https://example.com/jobs/123",
    "evidence": [{"keyword":"Salesforce","field":"description","snippet":"Maintain our Salesforce integrations."}]
  }]
}
```

Actual reports also include `sourceUrl` and a UTC `observedAt` timestamp. A complete
scan means all jobs in the returned response were examined and its reported total
matched the received count; it does not independently verify the employer's data.

### Limits and interpretation

- One board, 1–10 keywords of up to 60 characters each per run.
- At most 2,000 source jobs, 20 MB decoded HTTP response and 500 matching jobs.
- 45-second total source-request timeout; redirects are not followed.
- Exceeding a limit fails the scan without a partial report. If too many jobs
  match, use narrower keywords; oversized boards are unsupported.
- Source postings can be stale, incomplete or unavailable. A job listing is not
  proof of an open hiring process, an installed product, a budget or buying intent.
- Greenhouse only. No Lever, Workday, LinkedIn or private recruiting data.

You supply the board; this tool does not find all companies using a technology.
Repeated runs scan the current board again and are billed again. Scheduling and
integrations are available through Apify; this Actor itself sends no messages.

# Actor input Schema

## `boardToken` (type: `string`):

Slug only, not a URL. USD0.01 per completed board report including zero matches. Up to 2,000 jobs; oversized boards fail without a report.

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

1–10 keywords, up to 60 characters each. Case-insensitive word-boundary match in titles/descriptions; any keyword qualifies a job. More than 500 matching jobs fails without a partial report.

## Actor input object example

```json
{
  "boardToken": "figma",
  "keywords": [
    "Salesforce",
    "Snowflake"
  ]
}
```

# Actor output Schema

## `report` (type: `string`):

No description

## `summary` (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 = {
    "boardToken": "figma",
    "keywords": [
        "Salesforce",
        "Snowflake"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ecomopskits/greenhouse-job-keyword-evidence").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 = {
    "boardToken": "figma",
    "keywords": [
        "Salesforce",
        "Snowflake",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("ecomopskits/greenhouse-job-keyword-evidence").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 '{
  "boardToken": "figma",
  "keywords": [
    "Salesforce",
    "Snowflake"
  ]
}' |
apify call ecomopskits/greenhouse-job-keyword-evidence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ecomopskits/greenhouse-job-keyword-evidence"
        }
    }
}
```

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/1drPBnOgfiVFYHz1K/builds/oyf7hBD5PaZaZ89iS/openapi.json