Foundit Jobs Scraper

Collect public Foundit job listings across India and Southeast Asia for recruiting research, labor-market analysis, and scheduled job monitoring. Export stable job URLs, employers, locations, normalized salary and experience, skills, posting age, and native-versus-syndicated provenance.

Use cases

• Monitor newly posted roles by keyword and city.
• Track public hiring activity for a named employer.
• Compare salary, experience, and skill demand across Foundit markets.
• Feed normalized job records to spreadsheets, databases, dashboards, the Apify API, or MCP clients.

Input

Field	Purpose
keywords	Required job titles, skills, or search phrases.
market	Foundit country site: IN (default), SG, MY, or ID.
locations	Optional locations within the selected market.
company	Optional exact employer-name filter.
postedWithinDays	Keep jobs publicly dated within 1–60 days; listings without a public posting age are excluded when this filter is set.
maxItems	Stop after 1–1,000 unique jobs.
includeDescription	Fetch public detail pages when full descriptions are needed.

Example:

{"keywords":["software engineer"],"market":"IN","locations":["Bengaluru"],"postedWithinDays":7,"maxItems":100,"includeDescription":true}

Input recipes

Recent roles: combine one focused keyword, a market/location, and postedWithinDays. Rows without a public date are excluded so the monitor does not silently include unverifiable-old jobs.

Employer tracking: set company to the exact public employer name. The Actor compares names case-insensitively and omits unrelated employers.

Regional analysis: run the same keywords separately with market set to IN, SG, MY, or ID; locations should belong to the selected country site.

Fast monitoring: set includeDescription to false when card-level fields are sufficient. Enable it when full public descriptions are needed. If a detail page is unavailable or too slow to respond, the job is still saved with its listing fields; unavailable description fields remain empty.

Output

Each dataset item represents one public Foundit job. Core fields include id, url, applyUrl, title, companyName, locations, salary, experience, skills, description, postedAt, postingAgeDays, sourceType, and scrapedAt. Optional fields are null when Foundit does not publicly expose them; the Actor does not invent enrichment.

API, MCP, and integrations

Run the Actor from Apify Console, schedules, the Apify API, webhooks, or an MCP client. Read records from the default dataset as JSON, CSV, Excel, XML, RSS, or JSONL. Use id for deduplication and scrapedAt for collection provenance.

Pricing

The Actor uses pay-per-event pricing. The primary Job saved event is charged only when a public job record is successfully delivered to the dataset. See the live Pricing tab for current prices and plan-tier discounts; platform usage may apply according to your Apify plan.

Limitations and responsible use

Only anonymously accessible public Foundit search, listing, and employer surfaces are supported. The Actor does not use applicant data, recruiter-account data, login-only content, CAPTCHA bypasses, or job application automation. Fields vary by market and listing source. Foundit can change routes and access controls.

FAQ

Can I use this through the API or MCP?

Yes. All inputs are schema-defined and results are available from the default dataset.

Does it scrape private recruiter or applicant data?

No. It is limited to public job and employer information.

Why are some salary or skill fields empty?

Foundit does not expose every field on every listing. Missing public values remain null or empty arrays.

How should I monitor new jobs?

Use a narrow keyword/location query, set postedWithinDays, save the task, and schedule it in Apify.

Is this affiliated with Foundit?

No. This is an independent data extraction tool for public information.

Related Actors

For other hiring sources, try:

• LinkedIn Jobs Scraper
• Google Jobs Scraper
• Indeed Jobs Scraper
• Glassdoor Jobs Scraper
• JobStreet Job Listings Scraper

Support

Report reproducible issues with the input shape, affected public URL, expected behavior, and observed behavior. Never include credentials or private data.