# Lever Job Keyword Evidence Report (`ecomopskits/lever-job-keyword-evidence`) Actor

Find literal keyword mentions in published jobs on one global Lever board. Get source links and short excerpts in one bounded JSON report. USD0.01 per complete report, including zero matches; no browser or proxy.

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

## Pricing

$10.00 / 1,000 complete published lever board 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

## Lever Job Keyword Evidence Report

Find published jobs mentioning your chosen technologies or phrases on one public
Lever employer board. Get a JSON report with titles, locations, source links and
short text excerpts. For agencies and researchers who already know the board
and want a compact keyword report instead of reading every job description.

This is a literal text scan. Mentions can be requirements, comparisons or negated
statements. Read the excerpt and original posting before drawing conclusions
about hiring or technology use.

### Run a scan

Enter the exact site name from `https://jobs.lever.co/leverdemo` and 1–10 phrases.
Preserve capitalization; the site name may differ from the employer's name.
URLs themselves are not accepted. **Global Lever boards only**; boards hosted
at `jobs.eu.lever.co` are unsupported. `leverdemo` contains fictional demonstration
jobs and is an example input, not evidence of real vacancies.

```json
{"boardName":"leverdemo","keywords":["Salesforce","Python"]}
```

The Actor reads Lever's public published-postings API using `skip` and `limit`
until an empty page. It does not stop at a short page. Only public postings
returned by that API are scanned. It does not log in, discover employers, submit
applications or use a browser/proxy.

Matching is case-insensitive literal text with word boundaries: `Java` does not
match `JavaScript`. Phrases match normalized whitespace; punctuation must match.
Only exact duplicate keywords are removed after whitespace normalization.
Case variants remain distinct inputs and may produce separate evidence entries.
Unicode spellings such as `Straße` and `STRASSE` are not interchangeable matches.
Any keyword can qualify a job. Each keyword gets at most one excerpt per job,
preferring its first title match, otherwise its first description match.

Description text combines `descriptionPlain`, list headings and HTML list text,
then `additionalPlain`. Opening/body fields and HTML versions of plain fields
are not appended again. No stemming, synonyms, semantic classification or
cross-run history is provided.

### Output and price

One completed board report costs **USD0.01**, including zero matches
or a board without published jobs.
One report is one custom `board-report` event; no start or per-job event.
Input/source errors, unsupported response fields, exceeded limits or insufficient
event budget create no report and no custom event. 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 complete
`matches` and `evidence` arrays; this is not a flat spreadsheet export.
`SUMMARY` records completion, counts or the failure reason.

Synthetic one-job example (actual reports also include source URL and UTC time):

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

`scanComplete` means pagination reached an empty page and every received posting
was examined. Lever supplies neither a total count nor an atomic snapshot here.
A board that changes during pagination can omit postings; detected duplicate
IDs fail the scan, but this cannot detect every concurrent change. The report
does not independently reconcile the employer's listings or guarantee that
every open role is published. Counts describe the received postings.

### Limits

- One global board, 1–10 keywords of up to 60 characters each per run.
- At most 2,000 received postings, 20 MB total decoded HTTP responses and 500 matches.
- At most 8 MB serialized JSON per report; larger output fails before storage.
- 45-second total source timeout across all pages; redirects are not followed;
  no automatic retry.
- Oversized, failed or malformed responses fail without a partial report.
- Job data can be stale or incomplete. A mention is not proof of installed
  software, buying intent, a budget or an active hiring process.
- Public postings only; no dedicated salary/contact extraction or application
  data. Excerpts reproduce public posting text and may contain salary or contact
  details. Do not submit secrets or private content as keywords.

Repeated runs scan the current board again. Scheduling/integrations are Apify
features; this Actor itself sends no messages or maintains snapshots.

Source contract: [Lever Postings API](https://github.com/lever/postings-api).

# Actor input Schema

## `boardName` (type: `string`):

Global Lever site name only, not a URL; preserve capitalization. EU boards unsupported. USD0.01 per completed published-jobs report including zero matches or no jobs. Up to 2,000 source jobs; oversized boards fail without a report. The leverdemo example has fictional jobs.

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

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

## Actor input object example

```json
{
  "boardName": "leverdemo",
  "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 = {
    "boardName": "leverdemo",
    "keywords": [
        "Salesforce",
        "Snowflake"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ecomopskits/lever-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 = {
    "boardName": "leverdemo",
    "keywords": [
        "Salesforce",
        "Snowflake",
    ],
}

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ecomopskits/lever-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/vBrJBBjEurx6iO6RG/builds/HLI6pXNEPuMdwelle/openapi.json