Apna Job Detail Scraper
Pricing
from $3.99 / 1,000 results
Apna Job Detail Scraper
Extract public Apna.co job-detail and job-search postings with salary, organization, location, requirements, and JobPosting JSON-LD evidence.
Pricing
from $3.99 / 1,000 results
Rating
0.0
(0)
Developer
Coding Frontned
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Features
Share
Apna Job Detail Scraper
CSV inventory row: 4476. The implementation is aligned with the public Apna.co job-search and job-detail source represented by soft_alexist/apna-jobs-details-scraper.
What does Apna Job Detail Scraper do?
This Actor extracts publicly visible job postings from Apna.co. It accepts official search URLs or an individual public job URL, reads the server-rendered job feed and public JobPosting JSON-LD, and emits one source-backed dataset item per unique job. Search cards provide the job ID, title, company, location, salary range, tags, and public URL. When includeDetails is enabled, the Actor follows each public job URL and can add the description, employment type, date posted, expiry, experience, education, skills, department, work mode, and direct-apply metadata exposed by the page.
Why use Apna Job Detail Scraper?
- It uses direct, serialized HTTPS requests and works with Apna’s current SSR/Next.js feed without browser automation.
- It validates that requests and redirects remain on the official
apna.codomain. - It preserves card data when a detail page is unavailable and marks the fallback truthfully instead of inventing fields.
- It supports opt-in numbered pagination while keeping the original one-page default.
- It writes source-backed job rows and exact five-field diagnostics (
recordType,url,error,errorCode, andscrapedAt) for challenges, denials, empty pages, invalid URLs, and transient failures. - It excludes email addresses and sensitive contact/secret keys from extracted payloads. It never logs in, submits applications, or bypasses access controls.
How to use Apna Job Detail Scraper
Provide startUrls with values such as https://apna.co/jobs or a public URL copied from an Apna job card. If startUrls is empty, query builds an official search URL. The normal Apify workflow is:
apify validate-schemaapify run --input-file .actor/input.json
The Actor writes records to the default dataset and writes its aggregate run information to the OUTPUT_SUMMARY key-value-store record.
Input
startUrls is an array of official Apna search/detail URLs and retains the original string-list contract. query is an optional search phrase. maxJobs keeps its original meaning: the maximum unique candidates parsed from each search page. includeDetails defaults to true; set it to false for a fast card-only crawl. timeoutSecs and requestDelayMs control direct requests. maxPages defaults to 1 and can be increased to follow Apna’s ?page=N pagination. maxRetries covers only transient transport/5xx failures. maxResponseBytes bounds HTML responses. userAgent is an optional transparent override. fixtureFile is a development-only flat HTML or JSON file under test/fixtures or .actor/fixtures and disables network access for local testing.
Output
Each dataset item is either a source-backed Apna job record or a five-field diagnostic with exactly recordType, url, error, errorCode, and scrapedAt. Job rows contain public job, employer, salary, location, detail, and official-source URL fields; runtime, transport, inventory, record-wrapper, extraction-method, and local instrumentation fields stay in OUTPUT_SUMMARY or are omitted.
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Example job item:
{"source": "Apna.co public job posting","jobId": "756953653","jobTitle": "Inventory Executive( bangalore)","organizationName": "2Coms Consulting Pvt Ltd.","location": "All areas in Bengaluru/Bangalore Region","minSalary": 300000,"maxSalary": 420000,"currency": "INR","jobUrl": "https://apna.co/job/hoskote/inventory-executive-bangalore-756953653","sourceUrl": "https://apna.co/jobs","sourcePageUrl": "https://apna.co/jobs","searchUrl": "https://apna.co/jobs","sourceDomain": "apna.co"}
Data table
| Field | Description |
|---|---|
jobId, jobTitle, jobUrl | Stable public job identity |
organizationName, organizationLogo | Public employer identity |
location | Public Apna location text or structured address |
salary, minSalary, maxSalary, currency | Public INR salary information |
description, skills, experience, experienceText, education, shift | Detail-page fields when exposed |
industry, category, companyAddress, genderRequirement | Public role, employer, and requirement details |
earningPotential, tags, highlights, isWfh | Public compensation and job badges |
detailStatus, detailErrorCode | Whether optional public detail enrichment was fetched or failed |
sourceUrl, sourcePageUrl, searchUrl | Official public source URLs |
sourceDomain, source | Source attribution |
Pricing / Cost estimation
Apify platform compute and storage charges depend on the selected machine size, run duration, and dataset volume. This Actor makes no paid third-party requests and does not require a proxy. A card-only run generally uses one request per search page; enabling details adds at most one request per unique card. OUTPUT_SUMMARY.fallbackMode is no_fallback when all requested details were fetched, or public_search_card_fallback_for_detail when a usable search-card record is retained after a detail failure.
Tips or Advanced options
Use includeDetails: false for discovery, then rerun selected public detail URLs with details enabled. Increase maxPages gradually and add a small requestDelayMs for larger public crawls. Keep maxRetries low when diagnosing a source issue. A diagnostic is a useful signal that the source changed or denied access; it is not a job record.
FAQ, disclaimers, and support
The Actor only collects data visible on public Apna pages. It does not collect candidate profiles, private contact details, login-gated application data, or applicant authentication information. Search results and salaries can change after a run, and Apna may restrict automated access. Respect Apna’s terms, robots directives, applicable privacy law, and your permitted use of the data. For support, include the run ID, input URL, diagnostic code, and OUTPUT_SUMMARY values; never include credentials or private tokens.