# VeritaHire Verified Jobs Feed (`veritahire/veritahire-verified-jobs-feed`) Actor

US job postings read directly from employer career sites and kept live only while the employer lists them. Verification published live: requisition boards re-read within 36h, evergreen weekly, zero rows older than 14 days. Geocoded, categorised, pay text, mined skills. Not a scraper.

- **URL**: https://apify.com/veritahire/veritahire-verified-jobs-feed.md
- **Developed by:** [VeritaHire (1211 Holding LLC)](https://apify.com/veritahire) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Job Postings API — employer-direct, verified live, no scraping

**If you came here to scrape Indeed or LinkedIn, read this first.** Job-board scrapers pay for proxies, break when
the board changes, get blocked mid-run, and return the same posting five times from five aggregators — including
postings the employer closed weeks ago. This Actor is the other way round: the postings are read from
**employers' own career sites** before you ever run it, a posting is retired the moment the employer pulls it, and
the Actor simply returns the verified set with filters. No proxies. No blocks. A 500-row page is served in about 10 ms on our side.

- **~1.5 million live US postings** from ~7,000 employers across 126 ATS platform types (Workday, Greenhouse, Lever,
  iCIMS, SmartRecruiters, UKG, Ashby, Workable, employer-built sites).
- **Verified, and the number is published:** requisition boards re-read within 36 hours, evergreen (always-hiring)
  postings weekly, zero rows older than 14 days. Live measure: https://veritahire.com/jobdata.php
- **No ghost jobs by construction.** Not on the employer's board on our read = retired on that read. There is no
  "cleanup" step because expired postings are never admitted.
- 94% geocoded (lat/lng), pay text on ~40%, category / seniority / employment type / requirements / mined skills on
  nearly all, and `apply_url` goes to the **employer**, not to a board.
- **$2 per 1,000 results.** A 1,000-posting pull is $2.00 and finishes in seconds.

### Who uses it

- **Sales and GTM teams** — hiring signals by employer, state and category, without the re-post noise.
- **Labor-market and alt-data analysts** — a series where a vanished posting means the employer took it down,
  not that a scraper missed it. Per-employer daily hiring velocity is available on the direct API.
- **Job boards and matching products** — employer-direct apply links, no duplicate rows.
- **AI agents and automations** — run it from n8n, Make or Zapier via the Apify integration, or call it as an MCP
  tool through the Apify MCP server ("get verified postings for Lowe's in Texas").

### Input

| field | meaning |
|---|---|
| `maxItems` | how many postings to return (default 1,000; each is one result) |
| `state` | two-letter state, e.g. `CA` — blank for all |
| `category` | `retail_food`, `healthcare_clinical`, `sales`, `operations`, `skilled_trade`, `admin_support`, `software`, … |
| `remoteOnly` | only postings the employer flags remote |
| `employerId` | one employer (ids are in every row) |
| `platform` | `workday`, `greenhouse`, `lever`, `icims`, `smartrecruiters`, … |
| `postingKind` | `requisition` (a specific opening) or `evergreen` (always-hiring) |
| `since` | `YYYY-MM-DD` — postings first seen on or after this date |

### Output row

`job_id, employer, employer_id, title, location, state, lat, lng, remote, category, employment_type, seniority,
level_band, pay_text, comp_structure, req_edu_level, req_fields, req_hard_years, skills[], benefits, posting_kind,
platform, posted_at, first_seen_at, last_seen_in_feed, valid_through, apply_url, status`

Full job-description text is not included here (enterprise tier, under a signed order).

### Example

Input `{ "state": "TX", "category": "healthcare_clinical", "maxItems": 500 }` → 500 live clinical postings in Texas,
each with employer, geocode, pay text where stated, and the employer's own apply link. Export the dataset as JSON,
CSV or Excel, or read it from the API.

### Also available, direct from VeritaHire

Daily full + delta feed files, a keyed REST API with the same rows (free 2,000-record trial key, no card), and
per-employer daily hiring-velocity series. Pricing and trial: https://veritahire.com/verified-jobs-feed/ —
Docs: https://veritahire.com/data/API.md — Sample of 1,000 rows: https://veritahire.com/data/veritahire-jobs-sample-1000.csv

Licensor: 1211 Holding LLC (California, 2010). Contact: data@veritahire.com

# Actor input Schema

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

How many postings to return (each is one result).

## `state` (type: `string`):

Two-letter state, e.g. CA. Leave blank for all.

## `category` (type: `string`):

retail\_food, healthcare\_clinical, sales, operations, skilled\_trade, admin\_support, customer\_service, engineering\_hardware ...

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

Only postings flagged remote by the employer.

## `employerId` (type: `integer`):

Restrict to one employer (ids are in every row).

## `platform` (type: `string`):

workday, greenhouse, lever, icims, smartrecruiters ...

## `postingKind` (type: `string`):

requisition = a specific opening; evergreen = an always-hiring posting re-read weekly. Blank for both.

## `since` (type: `string`):

YYYY-MM-DD

## Actor input object example

```json
{
  "maxItems": 1000,
  "remoteOnly": false,
  "postingKind": ""
}
```

# Actor output Schema

## `postings` (type: `string`):

No description

## `postings_csv` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("veritahire/veritahire-verified-jobs-feed").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("veritahire/veritahire-verified-jobs-feed").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 '{}' |
apify call veritahire/veritahire-verified-jobs-feed --silent --output-dataset

```

## MCP server setup

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

```

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/ilH1Z7zfuG1xeYQbs/builds/zO9MqvY6iok2n5etK/openapi.json