FreeJobAlert India Govt Jobs Scraper

Collect Indian government, bank and railway job notifications from FreeJobAlert (freejobalert.com): post date, recruitment board, post name, qualification, advertisement number, last date and details link. Choose which site sections to read. Pay per result (see the Pricing tab). The residential proxy is built in.

What data you get

One dataset row per job notification (duplicates are removed by details link).

Field	Description
postDate	Date the notification was posted, as shown on the site (for example 23/06/2026)
recruitmentBoard	Recruiting organisation or board
postName	Exam / post name, often with the number of posts
qualification	Required qualification, as listed
advtNo	Advertisement number, when given
lastDate	Last date to apply, as shown on the site (for example 10-07-2026)
detailUrl	Link to the notification page on FreeJobAlert
section	The section slug the row came from
scrapedAt	ISO 8601 timestamp
parse_confidence	Share of core fields (recruitmentBoard, postName, detailUrl) that were found, 0 to 1

Dates are returned as text exactly as the site shows them. Empty cells are null.

How to use

1. Pick the sections you want. A section is the part of the address after freejobalert.com/, for example latest-notifications, bank-jobs, railway-jobs or engineering-jobs.
2. Enter them in Sections and set Max items.
3. Leave Proxy configuration on the default (Apify Residential, India). It is already set up; you need no extra account.
4. Click Start, then open the Job notifications table or export the dataset as JSON, CSV or Excel.

The actor reads the notification tables on each section page.

Input

Field	Type	Default	Description
sections	array of strings (required)	["latest-notifications"]	FreeJobAlert section slugs
maxItems	integer	200	Maximum notifications across all sections (0 = no cap)
proxyConfiguration	object	Apify Residential, country IN	Proxy settings. India is recommended for stable access

Example input:

{
  "sections": ["latest-notifications"],
  "maxItems": 200,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  }
}

Output example

Values below are illustrative.

{
  "postDate": "23/06/2026",
  "recruitmentBoard": "Example State Bank",
  "postName": "Probationary Officer – 500 Posts",
  "qualification": "Any Graduate",
  "advtNo": "CRPD/PO/2026-27/01",
  "lastDate": "08-07-2026",
  "detailUrl": "https://www.freejobalert.com/articles/example-bank-po-recruitment-2026",
  "section": "latest-notifications",
  "scrapedAt": "2026-10-02T09:30:00Z",
  "parse_confidence": 1.0
}

Use cases

• Sarkari naukri alerts: power a job-alert channel, newsletter or app with fresh government notifications.
• Job aggregation: add Indian public-sector, bank and railway openings to a job board.
• Recruitment calendars: use lastDate to build deadline reminders.
• Research: track which boards recruit, how many posts they announce and what qualifications they ask for.

FAQ

Do I need an API key or my own proxy? No. The residential proxy (India) is built in, and no login is needed. You do not need any API keys or external accounts.

How is it priced? Pay per result. See the Pricing tab for the current price per notification.

Which sections are available? Any section path that exists at freejobalert.com/<section>/ and shows notification tables, such as latest notifications, bank jobs, railway jobs or engineering jobs.

Is there a limit for free-plan runs? Runs on a free Apify plan return a preview of up to 25 results. Paid plans have no preview limit.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.