Foundit Jobs Scraper

Search public Foundit India job listings and return structured hiring data for recruiting, market research, job discovery, and AI workflows.

What it returns

Each validated dataset item includes the public job title, company, location, salary where shown, experience, employment type, industry, functional area, skills, description, posting date, and direct Foundit job URL.

Use it when you need public Foundit India listings by keyword and optional location. It does not apply for jobs, sign in, access candidate data, or bypass access controls.

Input

{
  "keywords": "data engineer",
  "location": "Bengaluru",
  "postedWithinDays": "7",
  "sortBy": "date",
  "maxResults": 50,
  "includeJobDetails": true
}

maxResults is both the result cap and the cap on row-level events. The actor charges $0.003 only after a complete, validated job record is persisted. One actor-start event is $0.005. Apify compute and residential-proxy usage are charged separately when Pay per event with platform usage pass-through is enabled.

Output and outcomes

Dataset rows are public job records. The default key-value store also contains:

• OUTPUT: compact machine-readable outcome and result count.
• RUN_SUMMARY: pages, write counts, charged events, warnings, and errors.

Terminal outcomes are COMPLETE, PARTIAL, VALID_EMPTY, INVALID_INPUT, UPSTREAM_FAILED, and CONFIG_ERROR. A blocked search with no useful result fails honestly; partial public results remain available as a successful partial outcome.

Limitations

Foundit can change its public page structure, ranking, pagination, and anti-bot controls without notice. Salary, skills, employer, dates, and detailed descriptions are included only when Foundit exposes them publicly. The actor uses a residential browser session and retires challenged sessions, but no scraper can guarantee access to every public listing.

When every direct Foundit route is challenged, the actor can use a configured SerpAPI Google Search fallback to return indexed public Foundit job URLs, titles, and snippets. This fallback is explicitly marked as partial when detail enrichment was requested.

Development

npm install
npm test
npm run build

Before deployment, configure Pay per event with isPPEPlatformUsagePaidByUser: true, then validate the final cloud build with the project's release-evidence workflow. Keep the actor private until the user adds an icon and explicitly publishes it.