# Instahyre foundit Scraper - India Job Vacancies, Salary, Skills (`snow_leo_data/instahyre-scraper`) Actor

India job listings from Instahyre and foundit (ex Monster India) in one search. Plain paging reaches about 9 994 Instahyre jobs (offset 9959 works, 9979 fails) of the 13 000+ open ones; this run walks each company-size bucket for the rest. Repeated pinned jobs are merged.

- **URL**: https://apify.com/snow_leo_data/instahyre-scraper.md
- **Developed by:** [Snow Leo Data](https://apify.com/snow_leo_data) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.60 / 1,000 job rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Instahyre & foundit Jobs Scraper — India tech jobs

Two India job boards in one run: **Instahyre** and **foundit** (ex Monster
India). Title, company, locations, skills and the link from both; salary range,
years of experience, employment type and industry from foundit.

No login, no cookies, no proxy.

### The ceiling, and how this run gets past it

Instahyre holds **13 419 open jobs** (the count moves daily), but plain paging cannot reach them all.
Measured by binary search on 18 Sep 2026: offset **9959 works, 9979 fails** — so
a scraper that only walks offsets stops at about **9 994 jobs** and silently
leaves a quarter of the board behind.

This run slices by company size instead. Measured live from the Apify cloud:

| Bucket | Jobs |
|---|---|
| 1 | 3 915 |
| 2 | 7 272 |
| 3 | 2 221 |
| **Together** | **13 419 of 13 419** |

Each bucket is below the ceiling, and together they cover the whole board.

**Every bucket is verified before it is used.** Instahyre silently ignores a
parameter name it does not know and returns the full set: `company_sizes=1`,
`size=small`, `employee_count=small` and `location=Bangalore` all came back with
the same 13 419. A scraper that trusted the name would walk the same list three
times and bill you three times for it. Here a bucket whose count equals the
whole is dropped, and the run says so in its report.

### You are not charged for repeats

foundit repeats one pinned job on **every** page. Measured: of 487 rows the
source handed over, **87 were repeats** — 18%. They are merged before delivery,
so they never reach your dataset and never appear on your bill.

foundit also stops advancing at `start=10000` and quietly serves the same page
again (checked at 10 000, 20 000 and 99 000 — identical job IDs). This run stops
at the measured ceiling instead of paying for circles.

### What a row holds

Common to both boards: `board`, `job_id`, `title`, `company`, `locations`,
`skills`, `url`.

Instahyre adds: `candidate_title`, `company_tagline`, `company_founded`,
`company_size`, `company_logo`, `posted_at`.

foundit adds: `min_salary`, `max_salary`, `salary_currency`, `salary_hidden`,
`min_experience`, `max_experience`, `employment_types`, `industries`,
`functions`, `designations`, `is_urgent`, `is_fresh`, `posted_ago`,
`created_at`, `last_updated`, `job_source`, `company_id`.

Types are the same on both boards on purpose: IDs are strings, skills are a
list. Mixing types makes a CSV unusable and made the very first cloud run of
this Actor fail outright.

#### Honest limits

- **Salary and years of experience come from foundit only.** Instahyre does not
  publish them at all, so a salary or experience filter with foundit switched
  off would drop every row — the run says that by name instead of finishing
  green and empty.
- **foundit needs a search word.** It has no browse-everything endpoint.
  Instahyre browses everything without one.
- Both boards rate-limit. The run paces itself and backs off; a full sweep of
  Instahyre takes a few minutes.

### Watch mode

Turn on **Only changed** and the run returns only jobs that are new or changed
since its previous run, labelled `NEW` or `UPDATED` with the changed fields
listed.

### Empty runs

A run that collects nothing **charges nothing** and says why by name in the run
log and in the `REPORT` record: no board selected, foundit without a search
word, a salary or experience filter without foundit, every row removed by
filters, nothing changed since the last run, or every board unreachable.

# Actor input Schema

## `boards` (type: `array`):

Which India job boards to read. Instahyre browses everything without a search word; foundit needs at least one.

## `queries` (type: `array`):

Search words for foundit, one per line. foundit has no browse-everything endpoint, so it needs at least one. Ignored by Instahyre unless Search word is set.

## `query` (type: `string`):

Optional. Leave empty to browse every open Instahyre job.

## `sliceByFunction` (type: `boolean`):

Instahyre serves only about 9 994 jobs through plain paging (measured: offset 9959 works, 9979 fails) out of 13 403. With this on, the run also walks each job function separately and reaches the rest.

## `maxItems` (type: `integer`):

Hard stop on billed rows. 0 means no limit.

## `minSalary` (type: `integer`):

Keep jobs whose upper salary is at least this. foundit only - Instahyre does not publish salary.

## `maxSalary` (type: `integer`):

Keep jobs whose lower salary is at most this. foundit only.

## `minExperience` (type: `integer`):

foundit only - Instahyre does not publish years of experience.

## `maxExperience` (type: `integer`):

foundit only.

## `locationContains` (type: `string`):

Keep jobs whose location contains this, case-insensitive. For example Bangalore.

## `companyContains` (type: `string`):

Keep jobs from companies whose name contains this.

## `titleContains` (type: `string`):

Keep jobs whose title contains this.

## `skillContains` (type: `string`):

Keep jobs whose skills contain this.

## `onlyChanged` (type: `boolean`):

For watch runs: return only jobs that are new or changed since the previous run of this Actor.

## `compact` (type: `boolean`):

Keep only the core columns, so the CSV has no empty ones.

## `timeoutSeconds` (type: `integer`):

How long one request to a board may take before it is retried.

## Actor input object example

```json
{
  "boards": [
    "instahyre"
  ],
  "queries": [
    "java"
  ],
  "sliceByFunction": true,
  "maxItems": 200,
  "minSalary": 0,
  "maxSalary": 0,
  "minExperience": 0,
  "maxExperience": 0,
  "onlyChanged": false,
  "compact": false,
  "timeoutSeconds": 30
}
```

# Actor output Schema

## `results` (type: `string`):

All collected jobs

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "boards": [
        "instahyre"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("snow_leo_data/instahyre-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "boards": ["instahyre"] }

# Run the Actor and wait for it to finish
run = client.actor("snow_leo_data/instahyre-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "boards": [
    "instahyre"
  ]
}' |
apify call snow_leo_data/instahyre-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,snow_leo_data/instahyre-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/2wGleuPyrLlJFTckl/builds/eZd4IbETwloLcndXk/openapi.json