# Employment News Scraper (`jobsapi/employmentnews-jobs-search-scraper`) Actor

Scrape job notifications from Employment News (employmentnews.gov.in), India's official weekly employment gazette published by the Ministry of Information and Broadcasting. Extract notification titles, categories, application deadlines, and eligibility for government job seekers.

- **URL**: https://apify.com/jobsapi/employmentnews-jobs-search-scraper.md
- **Developed by:** [Jobs API](https://apify.com/jobsapi) (community)
- **Categories:** Jobs, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 1,000 employment news notices

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Employment News Jobs Search Scraper

This Apify Actor reads the public [Employment News](https://employmentnews.gov.in) jobs table and joins each matching notification to its official advertisement PDF. It emits complete, source-grounded notification records rather than listing-only rows.

### Public input

```json
{
  "query": "recruitment",
  "maxItems": 3
}
```

`query` is matched against the public organisation, post, and appointment-method columns. `maxItems` is bounded to 1–50. The Actor uses ordinary direct access and exposes no proxy, stealth, fingerprint, retry, concurrency, fixture, or temporary context controls.

### Source workflow

1. Read `https://employmentnews.gov.in/NewEmp/AllJobs.aspx?k=All`.
2. Read the official Web Advertisement index at `https://employmentnews.gov.in/NewEmp/MoreContentS.aspx?n=WebAdvertisement`.
3. Match each selected organisation to its official PDF.
4. Fetch the PDF directly, record its hash, size, headers, page count, text-layer status, and source receipt, then emit the record.

Image-only official PDFs are reported as `pdfTextExtractionStatus: "IMAGE_ONLY"`; the Actor does not invent OCR text or substitute another source.

### Output

Each dataset record contains the five source table columns, normalized date objects, matching issue and advertisement metadata, official PDF integrity and extraction metadata, direct request receipts, stable URLs, and quality/provenance fields. The schema in `.actor/dataset_schema.json` is strict at the top level and accepts only fields produced by the Actor.

The run also stores `OUTPUT_SUMMARY`, `REQUEST_RECEIPTS`, `RUN_DIAGNOSTICS`, and `OUTPUT` in the default key-value store.

`status` reports the Apify process outcome (`SUCCEEDED` or `FAILED`); `resultStatus` separately reports data completeness (`COMPLETE`, `LIMITED`, `SKIPPED`, `DEFERRED`, `NO_DATA`, or `FAILED`). Only complete notifications that pass the first-party provenance/quality gate and whose awaited Dataset writes resolve are counted. If a later failure occurs after rows were stored, the platform run remains `SUCCEEDED` with `resultStatus: "LIMITED"`. Fatal zero-row runtime or storage failures call `Actor.fail()` and report `FAILED` / `FAILED`. Diagnostics and request receipts are KVS-only and never become Dataset rows.

Zero matching rows are `DEFERRED` unless the source itself provides a readable empty-results statement with a successful first-party receipt for every requested search. An empty parse alone is not positive `NO_DATA` evidence.

### Access policy

An explicit HTTP 401/403/429/451 response or verification/access-denial challenge from the official Employment News HTTPS domain stops the route and discards all staged records; the platform status is `SUCCEEDED` and `resultStatus` is `SKIPPED`. A denial/challenge on a non-first-party redirect, HTTP 407, other unverified responses, and browser/controller/transport failures are `DEFERRED`, not source blocks. If real rows were already stored before a later error, they are preserved as `SUCCEEDED` / `LIMITED`. The Actor does not switch proxies, identities, browser fingerprints, or alternate routes to work around a restriction.

### Local validation

```text
npm install
npm test
npm run lint
apify validate-schema
apify run --purge --input-file ./INPUT.json
npm run validate:dataset -- storage
```

The dataset validator requires successful source receipts, a matched official PDF, direct-source provenance, and more than 20 meaningful populated fields per emitted record.

# Changelog

This Actor's version history is a separate document: https://apify.com/jobsapi/employmentnews-jobs-search-scraper/changelog.md

# Actor input Schema

## `query` (type: `string`):

Keyword matched against the public organization, post, and appointment-method columns.

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

Maximum number of records with a matched official advertisement PDF.

## Actor input object example

```json
{
  "query": "recruitment",
  "maxItems": 3
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `requestReceipts` (type: `string`):

No description

## `diagnostics` (type: `string`):

No description

## `output` (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 = {
    "query": "recruitment"
};

// Run the Actor and wait for it to finish
const run = await client.actor("jobsapi/employmentnews-jobs-search-scraper").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 = { "query": "recruitment" }

# Run the Actor and wait for it to finish
run = client.actor("jobsapi/employmentnews-jobs-search-scraper").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 '{
  "query": "recruitment"
}' |
apify call jobsapi/employmentnews-jobs-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobsapi/employmentnews-jobs-search-scraper"
        }
    }
}
```

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/EFCLgLKvItYTN4lcf/builds/XWKPA9eLghLcZkdFQ/openapi.json