# Inhire Job Scraper (`datawatcher/inhire-scraper`) Actor

Scrapes job offers from inhire.io: salaries, contract types, work mode, experience levels, locations and the full description. Same output schema as our other Polish job portal actors.

- **URL**: https://apify.com/datawatcher/inhire-scraper.md
- **Developed by:** [DataWatcher](https://apify.com/datawatcher) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.34 / 1,000 job results

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

## InHire.io Jobs Scraper

Scrape **InHire.io jobs** from [inhire.io](https://inhire.io), the Polish job board for IT and business roles, and get clean data as JSON, CSV or Excel: **salaries** (also per month), **skills**, experience in years and level, contract types, locations and company. No browser, no login: it uses inhire.io's public JSON **API**, and you can run it from the Apify API too.

### 🔎 What does InHire.io Jobs Scraper do?

- Searches inhire.io by keywords, cities, categories, work type, experience level, contract type and "with salary only", or reads any listing or offer URL you paste.
- Returns one row per offer. With `extractFullDetails` on, each offer is read in full: description (text and HTML), benefits, street and coordinates, and the company profile (website, size, address, active offers, history).

### ⭐ Why this one

> **1️⃣ One schema across job portals.**
> All our job actors share one output schema and one input schema. Build your pipeline once: our other job actors ([NoFluffJobs](https://apify.com/datawatcher/nofluffjobs-scraper), [Just Join IT](https://apify.com/datawatcher/justjoin-scraper), [Pracuj.pl](https://apify.com/datawatcher/pracuj-scraper), [Bulldogjob](https://apify.com/datawatcher/bulldogjob-scraper), [RocketJobs.pl](https://apify.com/datawatcher/rocketjobs-scraper), [theprotocol.it](https://apify.com/datawatcher/theprotocol-scraper), [BlueLionJob](https://apify.com/datawatcher/bluelionjob-scraper), [Skillshot.pl](https://apify.com/datawatcher/skillshot-scraper), [Hollylist](https://apify.com/datawatcher/hollylist-scraper)) take the same input and return the same fields, so adding a portal means changing the actor name, not your code.

- **Low price, no start fee.** $0.40 per 1,000 offers; the other inhire.io scraper we found charges $2.00 and adds a start fee. You pay only for rows you get.
- **Salaries per month, plus the employer's own figures.** Each pay range starts with a monthly entry; a pay per hour or day also keeps the employer's own figures as a second entry (`isOriginal` true). Each entry has `min`, `max`, `currency`, `period`, `contractType` and `grossNet`. Gross or net follows the contract: employment is gross, B2B is net.
- **Experience as years and as a level.** Each offer gets `minYears` and a level: under 2 years junior, 2 to 4 mid, 5 and more senior. The years the description states win over the portal's dropdown figure.
- **Skills split into must-have and nice-to-have**, read from the requirements and nice-to-have sections of the description.
- **Remote and hybrid offers keep their city** when the portal gives one.
- **Rich company data:** with details on, each employer's inhire.io profile is read too (website, size, address, active offers, history).
- **Honest runs:** a run summary and a health status. A search that fails writes an unbilled diagnostic row.
- **Fast:** public JSON API, 50 offers per page, no browser.

### 🚀 How to scrape InHire.io jobs

1. Open the actor on Apify and click **Try for free**.
2. Fill in keywords, cities and filters, or paste an inhire.io listing or offer URL into `startUrls`.
3. Click **Start**.
4. Download the **InHire.io jobs data** as JSON, CSV or Excel from the Output tab, or fetch it with the Apify API.

### Data

This actor returns only what the site shows publicly at run time. We don't store or keep that data and are not its controller — you decide how you use it.

This is an independent tool, not affiliated with or endorsed by inhire.io; trademarks belong to their owners. It reads only public job pages: no login, no recruiter accounts. You are responsible for following inhire.io's terms and data-protection law (GDPR and others).

### 🤖 Use with AI agents (MCP)

AI assistants (Claude, ChatGPT, Cursor…) can run this actor through Apify's MCP server. Connect the server in your assistant, then ask, for example:

```text
Use the InHire.io Jobs Scraper to find senior data offers that are fully remote and show a salary. Show the 10 best-paid, with company, salary, period and link.
```

### 🔌 Run it your way

- **Schedule it** with Apify schedules for daily new-job feeds.
- **Call it from the Apify API** and its clients (Python, JavaScript).
- **Connect it** to Make, n8n, Zapier, webhooks or Google Sheets.
- **Ask an AI agent to run it**: see [Use with AI agents (MCP)](#-use-with-ai-agents-mcp).

### ⚙️ Input

Every job actor of ours takes the same inputs. Example: Python offers in Warsaw, B2B or employment, remote or hybrid, mid or senior, with full details:

```json
{
  "searchQueries": ["python"],
  "locations": ["Warszawa"],
  "contractTypes": ["b2b", "employment"],
  "workType": ["remote", "hybrid"],
  "experience": ["mid", "senior"],
  "maxResults": 50,
  "extractFullDetails": true
}
```

| Field | Default | Notes |
| --- | --- | --- |
| `maxResults` | `50` | Offers in total. `0` = no limit (the run timeout still applies). On the free Apify plan a run returns up to 1,000 offers |
| `startUrls` | – | inhire.io listing pages (`https://inhire.io/?locations=1&roles=it,business_analyst`) or offer pages (`https://inhire.io/praca/...`). A listing URL is read as that listing; an offer URL is always read from its own page. The filters below still apply to the rows |
| `searchQueries` | – | Keywords, one search per line (a technology, a company or a job title). The actor matches them on title, company and skills, since the site has no search term. Empty: every offer |
| `locations` | – | City names; accents and case do not matter (Krakow = Kraków = KRAKÓW). Empty: anywhere |
| `categories` | – | `backend`, `frontend`, `fullstack`, `mobile`, `devops`, `data`, `ai-ml`, `testing`, `security`, `it-admin`, `support`, `embedded`, `gamedev`, `erp`, `architecture`, `project-management`, `product`, `ux-ui`, `business-analysis`, `sales`, `marketing`, `hr`, `finance`, `customer-service`, `engineering`, `logistics`, `legal`, `administration`, `consulting`, `education`, `healthcare`, `construction` |
| `contractTypes` | – | `employment`, `b2b`, `mandate`, `specific-task` |
| `workType` | – | `remote`, `hybrid`, `onsite` (applied by the actor on the rows) |
| `experience` | – | `junior`, `mid`, `senior` (applied by the actor on the rows) |
| `withSalaryOnly` | `false` | Only offers that show a salary |
| `extractFullDetails` | `false` | Off: listing-level rows, cheaper and faster. On: each offer is read in full for the description, benefits, street and coordinates, skills and company profile. An offer URL is always read in full |
| `maxConcurrency` | `1` | Searches and detail pages processed in parallel |
| `maxRequestsPerMinute` | `60` | Request rate for the whole run |
| `proxyConfiguration` | off | Apify Proxy settings, useful when many detail pages are requested |
| `maxRequestRetries` | `2` | Retries after a failed request |

inhire.io lists about 565 offers in total, so one run without filters reads the whole board.

### 🧭 Input modes: what you give, what you get

One actor, six ways to use it. The mode follows from what you fill in.

| Mode | You give | Rows | Offer pages read |
| --- | --- | --- | --- |
| 🟢 **1. Default search** | nothing (empty input) | Newest offers, up to `maxResults` | Only with `extractFullDetails` on |
| 🔤 **2. Keyword search** | `searchQueries` | Offers matching the keywords | Only with `extractFullDetails` on |
| 🎛️ **3. Filtered search** | one or more filters, keywords optional | Offers matching the filters | Only with `extractFullDetails` on |
| 🔗 **4. Listing / search URL** | `startUrls` with a listing URL | That listing, as the site shows it | Only with `extractFullDetails` on |
| 📄 **5. One offer URL** | `startUrls` with an offer URL | That one offer | Always (a full row either way) |
| 🧩 **6. URLs + filters** | `startUrls` plus filters | Only rows matching the filters | Offer URLs always; listed offers only with `extractFullDetails` on |

Minimal input for each mode (real inputs from our test runs). Add `"extractFullDetails": true` to any of them for full rows.

#### 🟢 1. Default search

```json
{"maxResults": 3}
```

#### 🔤 2. Keyword search

```json
{"searchQueries": ["python"], "maxResults": 3}
```

#### 🎛️ 3. Filtered search

```json
{"searchQueries": ["python"], "locations": ["Warszawa"], "contractTypes": ["b2b", "employment"], "workType": ["remote", "hybrid"], "experience": ["mid", "senior"], "maxResults": 3}
```

#### 🔗 4. Listing / search URL

```json
{"startUrls": [{"url": "https://inhire.io/?locations=1&roles=it,business_analyst"}], "maxResults": 3}
```

#### 📄 5. One offer URL

```json
{"startUrls": [{"url": "https://inhire.io/praca/senior-businesssystems-analyst-remote-poland--job-arbeit-222279"}]}
```

#### 🧩 6. URLs + filters

```json
{"startUrls": [{"url": "https://inhire.io/?locations=1&roles=it,business_analyst"}, {"url": "https://inhire.io/praca/senior-businesssystems-analyst-remote-poland--job-arbeit-222279"}], "withSalaryOnly": true, "maxResults": 3}
```

With a start URL, the actor matches the rows against your filters itself.

### 📦 Output: InHire.io jobs data

A real row from an offer URL with details on (shortened; empty fields left out):

```json
{
  "recordType": "job",
  "source": "inhire",
  "id": "222279",
  "url": "https://inhire.io/praca/senior-businesssystems-analyst-remote-poland--job-arbeit-222279",
  "title": "Senior Business-Systems Analyst",
  "company": {
    "id": "connectis",
    "name": "Connectis",
    "url": "https://connectis.pl",
    "profileUrl": "https://inhire.io/pracodawca/connectis",
    "size": "200-500",
    "activeOffersCount": 43
  },
  "workType": [{"type": "remote", "remotePercent": 100, "remoteCountries": ["PL"]}],
  "categories": [{"value": "business-analysis", "original": "IT Analyst"}],
  "experience": {"levels": [{"value": "senior", "original": "5+", "minYears": 5, "source": "portal"}]},
  "contractTypes": [{"value": "b2b", "original": "contract", "source": "portal"}],
  "salaries": [
    {"contractType": "b2b", "currency": "PLN", "grossNet": "net", "min": 24864, "max": 26208, "period": "month", "isOriginal": false},
    {"contractType": "b2b", "currency": "PLN", "grossNet": "net", "min": 148, "max": 156, "period": "hour", "isOriginal": true}
  ],
  "skills": [
    {"name": "SQL", "required": true, "source": "portal"},
    {"name": "Jira", "required": false, "source": "description"}
  ],
  "languages": {"offer": "pl", "requirements": [{"code": "en", "level": "C1", "required": true}]},
  "description": {"text": "…", "html": "…"},
  "dates": {"posted": "2026-10-12", "expires": "2026-10-26", "scraped": "2026-10-26T19:12:44Z"},
  "extensions": {"applyUrl": "https://hub.connectis.pl/offer/…", "isRemoteRecruitment": true}
}
```

Missing data is `null`, never a guess. `dates.posted` and `dates.renewed` come from the offer's image stamp, so they are approximate. inhire.io has no data for `workTime`, `languages.recruitment`, `locations.postalCode` and `skills.level`: these stay `null`.

**Run status.** After each run, open the run's key-value store (Storage tab) to see how it went:

- **`RUN_HEALTH`**: `ok`, or `degraded` with the reason (no rows, a failed request, a warning, or a row that broke a data rule).
- **`RUN_SUMMARY`**: the run's numbers: rows, requests, retries, failed requests, warnings and billed events.

### 💰 Pricing (Pay-Per-Event)

| Event | Price | Trigger |
| --- | --- | --- |
| Result row (`job-scraped`) | $0.0004 (= $0.40 / 1,000) | Per offer returned |
| Details row (`job-details-scraped`) | +$0.0015 (= +$1.50 / 1,000) | Per offer read in full (`extractFullDetails` on, or an offer URL) |

No start fee: a run costs only the rows it returns. Diagnostic rows are never billed. Example: 1,000 offers with details = $0.40 + $1.50 = $1.90.

Free plan: each run returns up to 1,000 offers, with full details; paying Apify plans have no cap per run.

### 🎯 Use cases

- Track new openings for a role or stack on a daily schedule.
- Feed a job board aggregator or a personal job-search dashboard.
- Compare pay by contract type, city and experience level.
- Market research: which skills and seniority levels are in demand.
- Lead lists of hiring companies.
- Run the same pipeline over several Polish job portals, since they share one schema.

### ❓ FAQ

#### How many offers can I get?

As many as `maxResults` says (`0` = no limit). inhire.io lists about 565 offers, so one run can read the whole board.

#### How do I export InHire.io jobs to Excel or CSV?

Run the actor, open the Output tab and pick Excel or CSV in the export options. JSON, XML and HTML are there too, and the Apify API returns the same data.

#### How do I get InHire.io salary data?

Every offer row has a `salaries` list with `min`, `max`, `currency`, `period`, `contractType` and `grossNet`. Turn on `withSalaryOnly` to get only offers that show pay.

#### Can I combine it with other portals?

Yes. All our job actors share one output schema and one input schema, so rows from different portals fit one table. See the list below.

### 🔗 Other Polish job scrapers (same schema)

- [NoFluffJobs Jobs Scraper](https://apify.com/datawatcher/nofluffjobs-scraper)
- [Just Join IT Jobs Scraper](https://apify.com/datawatcher/justjoin-scraper)
- [Pracuj.pl Jobs Scraper](https://apify.com/datawatcher/pracuj-scraper)
- [Bulldogjob Jobs Scraper](https://apify.com/datawatcher/bulldogjob-scraper)
- [RocketJobs.pl Jobs Scraper](https://apify.com/datawatcher/rocketjobs-scraper)
- [theprotocol.it Jobs Scraper](https://apify.com/datawatcher/theprotocol-scraper)
- [BlueLionJob Jobs Scraper](https://apify.com/datawatcher/bluelionjob-scraper)
- [Aplikuj.pl Jobs Scraper](https://apify.com/datawatcher/aplikuj-scraper)
- [Skillshot.pl Jobs Scraper (video-game jobs)](https://apify.com/datawatcher/skillshot-scraper)
- [Hollylist Jobs Scraper (US entertainment jobs)](https://apify.com/datawatcher/hollylist-scraper)

### 💬 Feedback and custom work

Need another portal, a field or a custom feed? Open an issue on the Issues tab.

# Changelog

This Actor's version history is a separate document: https://apify.com/datawatcher/inhire-scraper/changelog.md

# Actor input Schema

## `maxResults` (type: `integer`):

Maximum number of offers returned, in total. 0 = no limit (the run timeout still applies). Free plan Apify users get at most 1000 offers per run, whatever is set here (paying users have no cap).

## `startUrls` (type: `array`):

URLs from which the actor starts scraping, instead of a search: a listing/search URL is read as that listing, a specific offer URL is read directly. locations, categories, contractTypes, workType, experience and withSalaryOnly still apply: rows that do not match are dropped. searchQueries is not applied (a warning says so).

## `searchQueries` (type: `array`):

Keywords to search for, one search per line (a technology or a job title). Empty - every offer.

## `locations` (type: `array`):

Only offers in these cities, written as normal city names; accents and case do not matter (Krakow = Kraków = KRAKÓW). A city the portal does not know gives a warning and no search for it, never an unfiltered search. Empty - anywhere.

## `categories` (type: `array`):

Only offers in these categories (the output's `categories[].value` values). Empty - all.

## `contractTypes` (type: `array`):

Only offers that allow one of these contracts (the output's `contractTypes` values). Empty - all.

## `workType` (type: `array`):

Only offers with one of these work types (the output's `workType[].type` values). Empty - all.

## `experience` (type: `array`):

Only offers for these experience levels (the output's `experience.levels[].value` values). Empty - all.

## `withSalaryOnly` (type: `boolean`):

Only offers that show a salary (the output's `salaries` is not empty). Off - all offers.

## `extractFullDetails` (type: `boolean`):

Fetch each offer's own page (and its company once per run) and return the full data: the description, skills, benefits, languages, company details. Off - listing-level data only, cheaper and faster. An offer start URL is always read. A filter whose field the listing lacks still reads that offer's page to decide.

## `maxConcurrency` (type: `integer`):

Maximum number of searches/details processed in parallel.

## `maxRequestsPerMinute` (type: `integer`):

Maximum HTTP request rate, for the whole run.

## `proxyConfiguration` (type: `object`):

Proxy settings, especially useful when many detail pages are requested.

## `maxRequestRetries` (type: `integer`):

Number of retries after a failed HTTP request.

## Actor input object example

```json
{
  "maxResults": 50,
  "searchQueries": [
    "python"
  ],
  "withSalaryOnly": false,
  "extractFullDetails": false,
  "maxConcurrency": 1,
  "maxRequestsPerMinute": 60,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "maxRequestRetries": 2
}
```

# Actor output Schema

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

One row per item.

## `runSummary` (type: `string`):

Rows, requests and budget, retries, failures, early stop, warnings, billing events, data-rule problems.

## `runHealth` (type: `string`):

{status, reason}: ok, degraded, or failed.

# 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 = {
    "searchQueries": [
        "python"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datawatcher/inhire-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 = { "searchQueries": ["python"] }

# Run the Actor and wait for it to finish
run = client.actor("datawatcher/inhire-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 '{
  "searchQueries": [
    "python"
  ]
}' |
apify call datawatcher/inhire-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datawatcher/inhire-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/VaQuMKwg4XxingaOl/builds/7o6vqGz6cdYNmmksC/openapi.json