FreeJobAlert India Govt Jobs Scraper | Sarkari Naukri avatar

FreeJobAlert India Govt Jobs Scraper | Sarkari Naukri

Pricing

from $2.57 / 1,000 job notifications

Go to Apify Store
FreeJobAlert India Govt Jobs Scraper | Sarkari Naukri

FreeJobAlert India Govt Jobs Scraper | Sarkari Naukri

Collect Indian government, bank and railway job notifications from FreeJobAlert. Get dates, boards, posts, deadlines. Run with sections, maxItems; no login or API key. Pricing: Free plan: $0.00265 per notification + $0.00005 per Actor Start event.

Pricing

from $2.57 / 1,000 job notifications

Rating

0.0

(0)

Developer

Vitalii Bondarev

Vitalii Bondarev

Maintained by Community

Actor stats

0

Bookmarked

28

Total users

4

Monthly active users

11 days ago

Last modified

Categories

Features

Limited permissions

Share

FreeJobAlert India Govt Jobs Scraper

Collect Indian government, bank and railway job notifications from public tables on FreeJobAlert (freejobalert.com), with dates, boards, posts, qualifications, deadlines and detail links. No login or API key is needed; requests use Apify Proxy with residential India by default, and runs on the Free plan return at most 25 notifications.

  • Choose sections such as latest-notifications, bank-jobs, railway-jobs and engineering-jobs, including multiple sections in one run.
  • Get one dataset row per notification, with duplicates removed by detailUrl or the recruitmentBoard and postName values together when no link exists.
  • Dates, boards and post names for alerts and newsletters.
  • lastDate for deadline calendars.
  • Aggregate Indian public-sector, bank and railway openings for a job board or research workflow.

What you get

The Actor reads notification tables on each selected FreeJobAlert section page. A field is null when the source does not provide the value; dates remain text exactly as shown on the site.

FieldTypeDescriptionNull or empty
postDatestringDate the notification was posted, as shown on FreeJobAlert; dates stay text as shown, with no conversionnull when the cell is empty or shows – or -
recruitmentBoardstringRecruiting organisation or boardnull is possible for one of recruitmentBoard and postName, never both, because a row with neither is dropped
postNamestringExam or post name, often including the number of postsnull is possible for one of recruitmentBoard and postName, never both, because a row with neither is dropped
qualificationstringRequired qualification, as listednull when the cell is empty or shows – or -
advtNostringAdvertisement number, when providednull when the cell is empty or shows – or -
lastDatestringLast date to apply, as shown on the sitenull when the cell is empty or shows – or -
detailUrlstringLink in the row's More Information cellnull when the row has no link
sectionstringSection slug from which the row was collected, with surrounding spaces removedNever null
scrapedAtISO 8601 string, UTC, YYYY-MM-DDTHH:MM:SSZUTC timestamp for the collected rowNever null
parse_confidencenumberShare of recruitmentBoard, postName and detailUrl that are not null, rounded to two decimalsNever null; values are 0.33, 0.67 or 1

Each returned row uses the fixed schema above. The dataset view is a table named Job notifications; section, scrapedAt and parse_confidence appear in the JSON and CSV export and in the API, not in the table view. Rows are de-duplicated within one run using detailUrl, or the recruitmentBoard and postName values together when no link exists.

Sample output

Example record from a run of this Actor:

{
"postDate": "09/10/2026",
"recruitmentBoard": "J&K Bank",
"postName": "Credit Auditor",
"qualification": "Retired Staff",
"advtNo": "No.S&C/CRAUDIT/CHQ/26",
"lastDate": "22-10-2026",
"detailUrl": "https://www.freejobalert.com/articles/j-k-bank-credit-auditor-recruitment-2026-apply-online-3072136",
"section": "latest-notifications",
"scrapedAt": "2026-10-09T05:41:05Z",
"parse_confidence": 1
}

Pricing

The current billing model charges you per event.

  • Job notification: one notification returned with all fields.
  • Actor Start: charged once per GB of run memory, minimum one event.

Prices differ by Apify plan:

PlanActor Start price on planJob notification price on plan
Free$0.00005 per event$0.00265 per notification
Bronze$0.0000495 per event$0.0026235 per notification
Silver$0.000049 per event$0.002597 per notification
Gold$0.0000485 per event$0.0025705 per notification
Platinum$0.000048 per event$0.002544 per notification
Diamond$0.0000475 per event$0.0025175 per notification

Free plan prices

NotificationsFree plan cost
10 notifications$0.0265 per 10 notifications
1,000 notifications$2.65 per 1,000 notifications
10,000 notifications$26.50 per 10,000 notifications

Free-plan runs return at most 25 notifications.

For a run with one Actor Start event (run memory of 1 GB or less), 10 results cost $0.02655 on the Free plan: 10 × $0.00265 + $0.00005 = $0.02655.

A full Free-plan run returns 25 notifications and, with one Actor Start event (run memory of 1 GB or less), costs $0.0663 (25 × $0.00265 + $0.00005); the $5 monthly credit covers 75 full runs (1,875 notifications).

You pay only for the events listed above. This Actor does not use the Pay per event + usage option, so the platform usage of your runs (compute, proxy traffic and storage) is not billed to you separately.

How to use

  1. Choose the FreeJobAlert section slugs you want to read.
  2. Enter the slugs in Sections and set Max items; the limit applies across all selected sections.
  3. Keep Proxy configuration on the default Apify Residential setting with country IN.
  4. Start the Actor.
  5. Open the Job notifications table to inspect the returned rows.
  6. Repeat the run through Apify Schedules, using daily as a starting point.

Example input:

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

Export the dataset as JSON or CSV, or read it through the Apify dataset API.

Input parameters

ParameterWhat it doesDefault
sectionsArray of FreeJobAlert section paths to scrape. An empty list falls back to ["latest-notifications"].["latest-notifications"]
maxItemsMaximum number of notifications across all sections. 0 means no cap before plan limits apply.200
proxyConfigurationProxy configuration used to reach FreeJobAlert.Apify Residential, country IN
disableUsageStatsSet to true to turn off the run summary described in Usage statistics.false

sections accepts section path strings rather than notification search terms. A section is the path after freejobalert.com/.

Limits and edge cases

ConditionWhat happensWhat to do
maxItems and the Free planThe cap counts saved, de-duplicated rows across all sections. maxItems defaults to 200 and has a minimum of 0. On the Free plan, the effective cap is min(maxItems, 25), or 25 when maxItems is 0; a paid plan removes the 25 cap. Results stop at the requested maximum across all selected sections.Set 0 to remove the cap only on a paid plan.
The same notification appears in multiple selected sectionsDuplicate rows are removed using detailUrl, or the recruitmentBoard and postName values together when no link exists. This applies within one run only.Select the sections you need; a matching key remains one dataset row.
A page contains no recognized notification tableA page of 3,000 characters or more that contains any <table is not blocked. If no table has both recruitment board and post name headers, it yields 0 rows and is not retried.Use a section path that exists and displays FreeJobAlert notification tables.
A transport error or blocked response occursHTTP status 401, 403, 429 or 503, a response body shorter than 3,000 characters, or a body with neither Recruitment Board nor <table is counted as blocked. If every attempt fails, the error is logged, the section is skipped and the run continues. A block, a network error or a page with no job table ends the run as Succeeded with an empty or short dataset. The reason is written only to the run log. The OUTPUT record in the default key-value store holds only totalJobs and sectionsRun.Keep the default India residential proxy, check the section slug and run again.
Rows are pushed or the run stops mid-runRows are pushed when 50 are ready and again at the end of each section page. Each push is followed by the charge for those rows. After an abort, timeout or failure mid-run, rows already pushed stay in the dataset and have been charged. Rows of the current section not yet pushed, fewer than 50 pending, are not saved or charged. The OUTPUT record is written only at the end, so it is missing after an abort.Run the Actor again to collect the remaining available rows.

FAQ

How much does it cost to scrape FreeJobAlert?

The Free plan charges $0.00265 per Job notification and $0.00005 per Actor Start event. For a run with one Actor Start event (run memory of 1 GB or less), 10 results cost $0.02655 on the Free plan, as shown in Pricing.

What happens if the run returns no notifications?

A page of 3,000 characters or more containing any <table but no recognized job table yields 0 rows and is not retried. If a block or network error prevents every attempt, the section is skipped and the run continues; the run ends as Succeeded with an empty or short dataset. The reason is kept in the run log, while the OUTPUT record contains only totalJobs and sectionsRun. Check that each selected path exists at freejobalert.com/<section>/, shows notification tables and uses the default India residential proxy configuration.

What should I do if a section is not working?

Each section page is fetched up to three times (three attempts in total), each with a new proxy session, after a wait of 1.5 s and then 3.0 s. One request times out after 50 s. Verify the section slug, keep the default proxy configuration, and run the Actor again; a section that remains unavailable is skipped while successfully pushed results remain in the dataset.

The Actor reads public job-notification tables from FreeJobAlert. Whether a particular collection or downstream use is legal or allowed depends on the source terms, applicable law and your use case; review those requirements yourself. This Actor does not provide a legal guarantee.

Usage statistics

This Actor creates a small, content-free summary at the end of each run, used only to monitor reliability and improve this Actor. No input values, credentials or scraped data are sent.

A copy of the exact record for your run is saved as USAGE_STATS in your own Apify key-value store.

To opt out, set disableUsageStats to true in the input. Nothing is sent then.

Full list of collected fields