SSC Recruitment Jobs Search Scraper

This Actor collects complete public recruitment notices from the official Staff Selection Commission APIs at ssc.gov.in. It enriches notices with exam metadata, publication dates, document attachments, source URLs, and candidate-portal information. It uses native HTTPS/JSON only and runs locally or in Apify Cloud. It does not log in, submit applications, use a proxy, bypass access controls, or access private endpoints. The current public API works directly without a proxy.

Supported modes

• search: one keyword matched against notice and exam metadata.
• searchMultiple: several keywords with notice-ID deduplication.
• single: one public notice ID.
• multiple: two or more public notice IDs.
• startUrls: official SSC notice-board page or notice-board API URL input.

The legacy query, keywords, and startUrl fields remain accepted.

Example input

{
  "mode": "search",
  "query": "recruitment",
  "maxItems": 3,
  "maxPages": 1,
  "includeAttachments": true,
  "includeRaw": true
}

Every emitted dataset row has a stable notice ID, title, notice kind, publication timestamp, at least one source-backed attachment, and complete official-source provenance. Null, blank, placeholder, duplicate, and diagnostic rows are excluded. If the official API is unavailable or a notice is incomplete, the run fails closed with zero partial dataset rows.

Output

Dataset rows use recordType: "sscRecruitmentNotice". RUN_SUMMARY stores counts and status; RUN_DIAGNOSTICS stores structured source/request/validation details; OUTPUT remains a compatibility alias for the summary.

Local development

npm ci --ignore-scripts --no-audit --no-fund
npm run check
npm test
apify validate-schema
apify run --purge --input-file INPUT.json
npm run validate

Set APIFY_LOCAL_STORAGE_DIR to use an isolated local run directory, then inspect its datasets/default/ and key_value_stores/default/ files.

Cloud deployment

After local validation, deploy with a bounded build wait using apify push --wait-for-finish 600 --json, then call the exact mapped Actor with a small input and inspect its dataset. Do not use a stale remote build as evidence for a changed local revision.

Run summaries identify local versus apify_cloud execution, request attempts, retries, and whether a proxy was used.