Apna.co Jobs Scraper

Extract verified Apna.co job listings at scale with flexible support for direct job URLs, keyword searches, city-based searches, and combined keyword-plus-location routes. Collect rich job data including salary ranges, openings, employer details, experience requirements, and structured location data for research, lead generation, and hiring intelligence.

Features

• Flexible input flow — Start from a working Apna job URL or search with keyword and location
• Rich job records — Collect titles, companies, salary ranges, openings, work mode, employer preferences, timestamps, and more
• Pagination control — Limit pages and output size for fast QA runs or larger production exports
• Clean dataset output — Empty and null-only values are removed before records are saved
• Broad route support — Works with type, city, keyword, and keyword-plus-city Apna job pages

Use Cases

Hiring Market Research

Track which roles are active in a city, how many openings are available, and what salary ranges employers are offering. Build city-level and role-level hiring snapshots quickly.

Sales Prospecting

Find companies actively hiring in specific functions such as software, finance, telesales, or delivery. Use structured employer and location data to enrich outreach lists.

Compensation Analysis

Compare salary bands across job types and locations. Use the extracted ranges to benchmark roles and identify hot markets.

Job Board Monitoring

Monitor public job activity on Apna across common route types and export consistent datasets for dashboards, alerts, or trend analysis.

Input Parameters

Parameter	Type	Required	Default	Description
url	String	No	—	Working Apna jobs URL. If provided, it overrides keyword and location.
keyword	String	No	software engineer	Job keyword or public route phrase.
location	String	No	—	City or region name shown on Apna.
results_wanted	Integer	No	20	Maximum number of jobs to save.
max_pages	Integer	No	5	Maximum number of paginated pages to visit.
proxyConfiguration	Object	No	Apify Proxy	Proxy settings for larger or more sensitive runs.
startUrl	String	No	—	Alias for url.
startUrls	Array	No	—	Optional list of candidate Apna jobs URLs.

Output Data

Each item in the dataset contains common fields such as:

Field	Type	Description
job_id	Integer	Unique Apna job ID
title	String	Job title
description_text	String	Plain text description
description_html	String	Sanitized internal HTML description
company	String	Employer name
url	String	Public Apna job URL
location	String	Main display location
city	String	City name when available
category	String	Job category
department_name	String	Department name
min_salary	Integer	Minimum salary
max_salary	Integer	Maximum salary
experience_in_years	String	Experience requirement summary
no_of_openings	Integer	Number of openings
job_address_line_1	String	Flattened job address
job_address_area	String	Flattened job area
job_address_city	String	Flattened job city
company_address_line_1	String	Flattened company address
company_address_area	String	Flattened company area
company_address_city	String	Flattened company city
work_mode	String	Work from office, work from home, or flexible
created_on	String	Job creation timestamp
expiry	String	Expiry date
ui_tags	Array	Visible job tags

Employer preference and international job flags are also flattened into simple fields when available.

Usage Examples

Direct URL Extraction

{
	"url": "https://apna.co/jobs/full_time-jobs",
	"results_wanted": 20,
	"max_pages": 3
}

Keyword and Location Search

{
	"keyword": "software engineer",
	"location": "Bengaluru/Bangalore",
	"results_wanted": 30,
	"max_pages": 4
}

City Route Collection

{
	"url": "https://apna.co/jobs/jobs-in-mumbai_bombay",
	"results_wanted": 50,
	"max_pages": 5,
	"proxyConfiguration": {
		"useApifyProxy": true,
		"apifyProxyGroups": ["RESIDENTIAL"]
	}
}

Sample Output

{
	"job_id": 539180069,
	"title": "Python Fullstack Developer",
	"description_text": "Sr. Python Full Stack Developer Bangalore Onsite - Immediate ...",
	"description_html": "<p>Sr. Python Full Stack Developer<br>Bangalore Onsite - Immediate</p>",
	"company": "Carpe Astra Technology LLP",
	"url": "https://apna.co/job/bengaluru-bangalore/python-fullstack-developer-539180069",
	"location": "Bengaluru/Bangalore",
	"city": "Bengaluru",
	"job_address_line_1": "Bangalore, Karnataka, India",
	"job_address_area": "Kailasipalyam",
	"job_address_city": "Bengaluru",
	"company_address_line_1": "Bangalore, Karnataka, India",
	"company_address_area": "Kailasipalyam",
	"company_address_city": "Bengaluru",
	"category": "Software / Web Developer",
	"department_name": "Software Engineering",
	"min_salary": 130000,
	"max_salary": 149999,
	"experience_in_years": "Min. 5 Years",
	"no_of_openings": 10,
	"work_mode": "Work from office",
	"created_on": "2026-04-10T00:00:00.000+00:00",
	"expiry": "2026-04-25",
	"ui_tags": [
		"Work from Office",
		"Full Time",
		"Min. 5 years",
		"Good (Intermediate / Advanced) English"
	]
}

Tips for Best Results

Use Public Apna Job Routes

• Use working URLs from Apna job pages for the most precise extraction.
• Supported patterns include job type routes, city routes, keyword routes, and keyword-plus-city routes.

Keep QA Runs Small

• Start with results_wanted: 20 and max_pages: 3 for quick validation.
• Increase limits after you confirm the route returns the jobs you want.

Match Apna Naming

• Keywords work best when they match public Apna route phrases such as software engineer, accounts finance, or full time.
• Use city names as shown on Apna, such as Bengaluru/Bangalore or Mumbai/Bombay.

Proxy Configuration

For reliable production runs, residential proxies are recommended:

{
	"proxyConfiguration": {
		"useApifyProxy": true,
		"apifyProxyGroups": ["RESIDENTIAL"]
	}
}

Integrations

• Google Sheets — Export job data for quick analysis
• Airtable — Build searchable recruiting datasets
• Make — Automate downstream processing and alerts
• Zapier — Push new listings into CRM or messaging workflows
• Webhooks — Deliver fresh datasets to internal systems

Frequently Asked Questions

Can I use a direct Apna URL instead of keyword and location?

Yes. If you provide url, the actor uses that route directly and ignores keyword and location.

What if my keyword does not match a public Apna route?

The actor tries the closest valid route and continues with keyword filtering when needed, but exact public route phrases will always be more precise.

Does the dataset include null values?

No. Empty and null-only fields are removed before records are stored.