# Hospitality Jobs Scraper · 4 Boards, One Schema (`bibian/hospitality-jobs-scraper`) Actor

Hospitality jobs: hotel and restaurant job postings from L'Hôtellerie Restauration (France), HOGAPAGE and Gastrojobs (Germany) and Hosco (worldwide) in one run, one schema, deduplicated across sources, no login.

- **URL**: https://apify.com/bibian/hospitality-jobs-scraper.md
- **Developed by:** [Vivien MORVAN](https://apify.com/bibian) (community)
- **Categories:** Jobs
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.96 / 1,000 job postings

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

## Hospitality Jobs Scraper · 4 Boards, One Schema

Extract hospitality and restaurant job postings in a single run from [L'Hôtellerie Restauration](https://www.lhotellerie-restauration.fr) (France), [HOGAPAGE](https://www.hogapage.de) (Germany), [Gastrojobs](https://www.gastrojobs.de) (Germany) and [Hosco](https://www.hosco.com) (worldwide) — mapped to one unified schema, deduplicated across sources. No login, no browser to configure.

### What you can do with it

- **Search hotel, restaurant and catering jobs across France, Germany and the rest of the world in one run**, instead of buying and maintaining 4 separate scrapers.
- **Filter once, everywhere**: `keywords`, `location`, `remote` and `publishedWithinDays` apply the same way across all 4 sources.
- **Narrow by country**: `countries` keeps only the boards covering France, Germany, or Hosco's worldwide listings.
- **Monitor new postings daily**: schedule it with `onlyNew` checked and `publishedWithinDays: 1` to get, and pay for, only what is new since the last run.

### Input

| Field | What it does |
|---|---|
| `keywords` | Job title or trade, for example `chef de cuisine` or `Koch`. Empty means every posting. |
| `location` | City or region, for example `Paris` or `Berlin`. Empty means all locations. |
| `countries` | Which countries to cover: `FR`, `DE`, `GLOBAL` (Hosco). Defaults to all 3. |
| `sources` | Which of the 4 job boards to query in this run. Defaults to all 4. |
| `publishedWithinDays` | Keep only postings published in the last N days. Use `1` for a daily monitoring run. |
| `remote` | Keep only postings with this remote policy: `any`, `remote`, `hybrid` or `onsite`. |
| `maxItems` | The run stops once this many postings are saved, across all sources combined (default 20 — Hosco's robots.txt imposes a 10-second delay between requests, which caps how many of its postings fit in one run). |
| `includeDescriptions` | Add the job description as plain text (default on). |
| `onlyNew` | For scheduled runs: skip postings an earlier run of this same search already delivered. |

### Output

One record per posting, in the schema shared by every job actor on this account:

| Field | Type | Meaning |
|---|---|---|
| `id` | string | Stable identifier (`<source>:<native id>`), used to deduplicate between runs. |
| `url` | string | Public page of the posting. |
| `title` | string | Job title as published. |
| `companyName` | string or null | Employer name; `null` when hidden (then `confidentialCompany: true`). |
| `companyUrl` | string or null | Company page on the source site, when it exists. |
| `locationLabel` | string or null | Location as displayed by the site. |
| `city` | string or null | City. |
| `region` | string or null | Region, Land or equivalent. |
| `postalCode` | string or null | Postal code. |
| `country` | string | ISO 3166-1 alpha-2 country code (`FR`, `DE`, or the employer's own country for Hosco's worldwide postings). |
| `remote` | string | `remote`, `hybrid`, `onsite` or `unknown`. |
| `employmentType` | string | `full_time`, `part_time`, `contract`, `freelance`, `internship`, `apprenticeship`, `temporary` or `unknown`. |
| `salaryMin` / `salaryMax` | number or null | Salary range, as numbers. |
| `salaryCurrency` | string or null | ISO 4217 currency code. |
| `salaryPeriod` | string or null | `hour`, `day`, `month` or `year`. |
| `datePosted` | string or null | Publication date, ISO 8601. |
| `validThrough` | string or null | Expiry date, ISO 8601. |
| `description` | string or null | Plain-text description, only when `includeDescriptions` is on. No personal data. |
| `experienceLevel` | string or null | As named by the site. |
| `industry` | string or null | As named by the site. |
| `skills` | string\[] | Skills listed by the site, if any. |
| `source` | string | Host name of the source site. |
| `sourceId` | string | Native identifier on the source site. |
| `scrapedAt` | string | Extraction timestamp, ISO 8601. |

### Why this one

4 sector-specific boards in one run, one schema, deduplicated across sources by URL and by (title, company, city). `source` and `country` on every row to filter or split by board or market. No connection, no login, no browser to configure.

### Good to know

- Hosco is throttled on purpose: its robots.txt sets a 10-second delay between requests, which this actor respects, so it contributes fewer postings per run than the other 3 boards.
- `employmentType` and `remote` are read from each site's own fields when it has one, and left `unknown` rather than guessed when nothing matches.
- No personal data: contact details of individuals are stripped from descriptions; only companies are named. CV and candidate-profile pages are never read.

### Pricing

Pay per result: **$3.70 per 1,000 postings**, plus a small start fee. You only pay for the postings you receive, deduplicated across all 4 sources before being counted or charged. Store discounts apply automatically on paid Apify plans: up to 20% off every event on the higher tiers.

### Run it from your code

JavaScript:

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('bibian/hospitality-jobs-scraper').call({
  keywords: 'chef de cuisine',
  maxItems: 20,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

Python:

```python
from apify_client import ApifyClient

client = ApifyClient(token="<APIFY_TOKEN>")
run = client.actor("bibian/hospitality-jobs-scraper").call(run_input={
    "keywords": "chef de cuisine",
    "maxItems": 20
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
```

### Monitor new postings daily and connect your tools

1. **Schedule it.** Save a task, set its publication date filter to the shortest window, and schedule it daily with Apify Schedules. Tick **Only new results** in the input and each run returns, and charges, only the postings that earlier runs of the same search did not deliver.
2. **Push the results where you work.** Add an Apify integration or a webhook to the task: Google Sheets, Slack, Make, Zapier, n8n or your own endpoint, triggered at the end of every run.
3. **Call it from your stack.** The API and the JavaScript and Python clients return the dataset as JSON, CSV or Excel.
4. **Let an AI agent use it.** Through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp), assistants such as Claude or ChatGPT can search the Store, read this page and run the actor as a tool.

### Frequently asked questions

**Do I need an account, cookies or a proxy?** No. The actor reads publicly visible pages only.

**Why does Hosco return so few results compared to the other boards?** Hosco's own robots.txt sets a 10-second delay between requests; this actor respects it, which limits how many of its postings fit in a single run's time budget.

**Which formats can I export?** JSON, CSV, Excel, XML, HTML table or RSS, from the dataset page or through the API.

**Is it legal to scrape?** The actor collects publicly visible postings and respects the robots.txt rules of each site. How you use the data is your responsibility: check each site's terms and the laws that apply to you, for example the GDPR.

**Something does not work?** Open an issue in the Issues tab. Every public actor is test-run daily and the broken ones are repaired.

**Did this save you time?** A short review on the Store page helps other people find the actor, and tells me what to improve next.

### Who uses it

- **Recruiting agencies and HR teams** watch which companies hire, for which roles and at which salary, in their market.
- **Job boards and aggregators** feed their own site with fresh postings in a stable schema, without maintaining a parser.
- **B2B sales and lead generation**: a company that is hiring is a company that is buying. Filter postings by role to spot prospects early.
- **Labour-market research**: salaries, skills in demand, remote share and hiring volume over time.

### Pricing

Pay per result: **$3.70 per 1,000 postings**, plus $0.01 per run start with the default 4 GB of memory. For example, 100 postings cost about $0.38. You only pay for the postings you receive, and platform usage is included in that price. Store discounts apply automatically on paid Apify plans: up to 20% off every event on the higher tiers.

### Run it from your code

JavaScript:

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('bibian/hospitality-jobs-scraper').call({
  maxItems: 50,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

Python:

```python
from apify_client import ApifyClient

client = ApifyClient(token="<APIFY_TOKEN>")
run = client.actor("bibian/hospitality-jobs-scraper").call(run_input={
    "maxItems": 50
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
```

### Monitor new postings daily and connect your tools

1. **Schedule it.** Save a task, set its publication date filter to the shortest window, and schedule it daily with Apify Schedules. Deduplicate on the `id` field if you keep your own copy. Tick **Only new results** in the input and each run returns, and charges, only the postings that earlier runs of the same search did not deliver.
2. **Push the results where you work.** Add an Apify integration or a webhook to the task: Google Sheets, Slack, Make, Zapier, n8n or your own endpoint, triggered at the end of every run.
3. **Call it from your stack.** The API and the JavaScript and Python clients return the dataset as JSON, CSV or Excel.
4. **Let an AI agent use it.** Through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp), assistants such as Claude or ChatGPT can search the Store, read this page and run the actor as a tool.

### Frequently asked questions

**Do I need an account, cookies or a proxy for Hospitality?** No. The actor reads publicly visible pages only.

**Which formats can I export?** JSON, CSV, Excel, XML, HTML table or RSS, from the dataset page or through the API.

**Is it legal to scrape?** The actor collects publicly visible postings and respects the robots.txt rules of the site. How you use the data is your responsibility: check the site's terms and the laws that apply to you, for example the GDPR.

**Need another site, a missing field or a new filter?** Open an issue in the Issues tab and say what you need, with an example URL if you have one. Requests are read, and the most asked ones are built next.

**Need a custom version built for you?** I also build private versions and custom scrapers: another site, extra fields, a specific output format, or delivery straight to Google Sheets, a database or a webhook. Open an issue in the Issues tab with what you need and an example URL, and I will reply there with a quote.

**Something does not work?** Open an issue in the Issues tab. Every public actor is test-run daily and the broken ones are repaired.

**Did this save you time?** A short review on the Store page helps other people find the actor, and tells me what to improve next.

### More job scrapers by the same author

- [Free-Work Jobs & Freelance Missions Scraper (France)](https://apify.com/bibian/free-work-jobs-scraper)
- [Infoempleo Jobs Scraper (Spain)](https://apify.com/bibian/infoempleo-jobs-scraper)
- [Arbeitsagentur Jobs Scraper (Germany)](https://apify.com/bibian/arbeitsagentur-jobs-scraper)
- [Bumeran, Zonajobs & Laborum Jobs Scraper (LatAm)](https://apify.com/bibian/latam-jobs-bumeran-scraper)
- [Universal Job Postings Scraper (any job site)](https://apify.com/bibian/universal-job-postings-scraper)
- [Codeur.com Freelance Projects Scraper (France)](https://apify.com/bibian/codeur-projects-scraper)

# Actor input Schema

## `keywords` (type: `string`):

Job title or trade, for example "chef de cuisine" or "Koch". Leave empty to get every posting.

## `location` (type: `string`):

City or region, for example "Paris" or "Berlin". Leave empty for all locations.

## `countries` (type: `array`):

Keep only the sources covering these countries. "Worldwide" keeps Hosco regardless of the other countries chosen, since it is not tied to a single one.

## `sources` (type: `array`):

Job boards to query in this run.

## `publishedWithinDays` (type: `integer`):

Keep only postings published in the last N days. Use 1 for a daily monitoring run. Leave empty for no limit.

## `remote` (type: `string`):

Keep only postings with this remote policy.

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

The run stops once this many postings are saved, across all sources combined. Kept low by default: Hosco's robots.txt imposes a 10-second delay between requests (politeness rule), which caps how many of its postings fit in one run.

## `includeDescriptions` (type: `boolean`):

Add the job description as plain text.

## `onlyNew` (type: `boolean`):

For scheduled runs. Skip the results that an earlier run of this same search already delivered, so each run returns, and charges, only what is new. The memory is kept in a key-value store of your account named "only-new-memory-bibian-" followed by the ID of this Actor.

## Actor input object example

```json
{
  "keywords": "",
  "location": "",
  "countries": [
    "FR",
    "DE",
    "GLOBAL"
  ],
  "sources": [
    "lhotellerie",
    "hogapage",
    "gastrojobs",
    "hosco"
  ],
  "remote": "any",
  "maxItems": 20,
  "includeDescriptions": true,
  "onlyNew": false
}
```

# Actor output Schema

## `postings` (type: `string`):

No description

# 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 = {
    "keywords": "",
    "location": "",
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("bibian/hospitality-jobs-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 = {
    "keywords": "",
    "location": "",
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("bibian/hospitality-jobs-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 '{
  "keywords": "",
  "location": "",
  "maxItems": 20
}' |
apify call bibian/hospitality-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bibian/hospitality-jobs-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/MsXp7MTqwvShr8r9F/builds/bq94J2ptalwRFrdIS/openapi.json