# Caterer.com UK Hospitality Jobs Scraper (/w EMAILS) (`memo23/caterer-scraper`) Actor

Scrape 5,900+ UK hospitality jobs from Caterer.com — chef, restaurant, hotel, events — via official mobile API. Filters: keyword, location, posted-within, employer-type, min-salary, job-type. Rows: title, employer + logo, structured salary, lat/lng, applyUrl

- **URL**: https://apify.com/memo23/caterer-scraper.md
- **Developed by:** [Muhamed Didovic](https://apify.com/memo23) (community)
- **Categories:** Jobs, Automation, Agents
- **Stats:** 22 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.90 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Caterer.com UK Hospitality Jobs Scraper

Scrape **UK hospitality job postings** from **Caterer.com** — chef, restaurant manager, hotel staff, events, sous-chef, bar manager. Every row carries title, employer + logo, location with lat/lng, **structured salary band** (min / max / currency / period), `datePosted`, `validThrough`, employment type, industry, and a populated `applyUrl` when the role is direct-apply. One flat row per job from rich `JobPosting` JSON-LD plus structured salary metadata.

![How Caterer.com Scraper works](https://raw.githubusercontent.com/muhamed-didovic/muhamed-didovic.github.io/main/assets/how-it-works-caterer.png)

### Why this actor

Caterer.com is the dominant UK hospitality-vertical job board — chefs, restaurant managers, hotel staff, and events roles. ~5,900 live London hospitality postings at any time, server-side scoped to the hospitality vertical so you get exactly what Caterer.com's web UI shows.

- **Hospitality-only result set** — the actor's request is scoped to hospitality roles (chef, restaurant, hotel, events, bar staff) so you don't pay for irrelevant general-UK rows. Matches Caterer.com's web search exactly
- **Efficient JSON listing pagination** at 50 items per page, with `totalItems` reported up-front so we know exactly when we've reached the end
- **Server-side filters** — `postedWithin` (1 / 3 / 7 / 14 days), `companyTypes` (direct employer / agency), `salary` (minimum), and `jobType` (permanent / contract / temporary / part-time / work-from-home) all honoured server-side
- **Apify Residential GB** for the per-job detail fetch — the only proxy pool that consistently returns 200 OK on UK job-board detail pages
- **JobPosting JSON-LD parsing** — every row carries the full 14-field JSON-LD detail plus structured salary metadata. Hospitality jobs commonly use **hourly** rates (£12.50/hour, £14.80/hour) and the structured `period` field captures that cleanly
- **`applyUrl` populated** when `directApply: true` (≈ 60–70 % of jobs) — the candidate-facing apply URL, not just the search-page URL
- **Mixed input** — listing URLs auto-paginate + emit one row per detail; direct detail URLs scrape one row each

### Use cases

- **Hospitality recruitment market intelligence** — salary benchmarking for chef, hotel manager, F\&B roles by region; track which restaurant groups are actively hiring
- **Restaurant / hotel chain competitive analysis** — see what your competitors are paying for sous-chefs, F\&B managers, event managers
- **Hospitality staffing agencies** — feed the structured rows into your placement workflow
- **Industry research** — track UK hospitality job market trends (post-pandemic recovery, immigration impact, regional differences)
- **Geospatial analytics** — every row carries `location.lat` + `location.lng` for mapping hotel/restaurant hiring hotspots
- **Hourly-wage analytics** — Caterer.com is one of the rare UK job boards where hourly salary data is rich; use `salary.period === "hour"` filtering for accurate hourly-rate analysis

### Input

| Field | Type | Required | Notes |
|---|---|---|---|
| `startUrls` | `string[]` | yes | Mix of listing URLs (`https://www.caterer.com/jobs/in-london`, `/jobs/chef/in-london`) and direct detail URLs. Filters supported in the query string: `?postedWithin=1\|3\|7\|14`, `?companytypes=1\|2`, `?salary={int}`, `?jobType=permanent\|contract\|temporary\|partTime\|workFromHome`. |
| `maxItems` | `integer` | no | Maximum job rows emitted **per listing URL**. Each row = one paid dataset item. Default `1000`. Free-tier users have a hidden global ceiling of `100` rows. |
| `maxConcurrency` | `integer` | no | Parallel HTTP requests for detail-page fetches. Sweet spot 3–5 via Apify Residential GB. Default `4`. |
| `maxRequestRetries` | `integer` | no | Per-URL retry budget on proxy CONNECT failures, HTTP/2 stream resets, and network errors. Default `6`. |
| `proxy` | object | no | **Apify Residential GB required** for the detail-page fetch. Default is wired correctly — don't override unless you know what you're doing. |

#### Example input

```json
{
  "startUrls": [
    "https://www.caterer.com/jobs/chef/in-london",
    "https://www.caterer.com/jobs/in-manchester?postedWithin=7&companytypes=2"
  ],
  "maxItems": 200,
  "maxConcurrency": 4,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "GB" }
}
```

### Output schema

Every row has `rowType: "job"`. **14 fields from JSON-LD + structured salary band (often hourly for hospitality) + lat/lng + applyUrl.**

```jsonc
{
  "rowType":           "job",
  "sourceSearchUrl":   "https://www.caterer.com/jobs/in-london",
  "jobId":             "107379957",
  "jobUrl":            "https://www.caterer.com/job/commi-chef/novotel-london-brentford-job107379957",
  "sourceSite":        "caterer.com",
  "title":             "Commi Chef",

  // ── JobPosting JSON-LD ──
  "description":       "<p>We are looking for a passionate Commi Chef to join our team at Novotel London Brentford…</p>",
  "datePosted":        "2026-05-20T14:32:18.000Z",
  "validThrough":      "2026-06-30T14:32:18.000Z",
  "employmentType":    "FULL_TIME",
  "industry":          "Hospitality, Hospitality-Restaurants and Catering",
  "directApply":       true,
  "jobLocationType":   null,
  "applicantLocationRequirements": [],

  // ── Employer ──
  "employer": {
    "name":            "Novotel London Brentford",
    "url":             "https://www.caterer.com/jobs/novotel-london-brentford?cmpId=%E2%80%A6",
    "logoUrl":         "https://www.caterer.com/CompanyLogos/%E2%80%A6novotel.png"
  },

  // ── Location ──
  "location": {
    "text":            "Brentford, London, GB",
    "locality":        "Brentford",
    "region":          "London",
    "postalCode":      null,
    "country":         "GB",
    "lat":             51.48717,
    "lng":             -0.30957
  },

  // ── Salary (often HOURLY for hospitality) ──
  "salary": {
    "rawText":         "£14.80 per hour",
    "min":             14.80,
    "max":             null,
    "currency":        "GBP",
    "period":          "hour"
  },

  // ── Apply flow ──
  "applyUrl":          "https://www.caterer.com/job/commi-chef/novotel-london-brentford-job107379957",
  "applyType":         "internal",

  "scrapedAt":         "2026-05-21T20:25:31.012Z"
}
```

### Apply flow — what `applyUrl` and `applyType` mean

| `directApply` | `applyType` | `applyUrl` | Meaning |
|---|---|---|---|
| `true` | `"internal"` | **= `jobUrl`** | Caterer hosts a one-click apply form on the job page itself. |
| `false` | `"external"` | `null` | External recruiter ATS (e.g. the hotel chain's careers portal). Open `jobUrl` in a browser and click *Apply* to be redirected. |
| missing | `"unknown"` | `null` | JSON-LD didn't surface the flag. Treat the same as `"external"`. |

**Practical rule of thumb:** ≈ 60–70 % of Caterer.com listings are `directApply: true`.

### Notes & limitations

- **Hourly salaries are common.** Unlike most UK job boards where £-per-annum dominates, Caterer.com has a healthy mix of hourly rates. The structured `salary.period: "hour"` field captures that — use it for accurate per-hour analysis.
- **Apify Residential GB is mandatory** for the per-job detail fetch.
- **`employmentType` fill is HIGHER on Caterer than on general boards** (≈ 85%) — hospitality employers tend to declare PART\_TIME / FULL\_TIME more reliably because shift structure matters more in the industry.
- **`jobLocationType` rarely populated.** Hospitality is overwhelmingly on-site, so `null` is the norm.
- **No radius-based filter.** Use a tighter `where=` location instead.
- **No maximum-salary filter.** Only minimum (`?salary=N`).

### FAQ

**Which Caterer.com URLs work?**
Two types: **listing URLs** (`/jobs/in-london`, `/jobs/chef/in-london`, `/jobs/{company-slug}-jobs`) which auto-paginate, and **direct detail URLs** (`/job/{title-slug}/{org-slug}-job{id}`) which scrape one row each.

**Why is my salary rate £12 instead of £25,000?**
Hospitality jobs are often paid hourly. The `salary.period` field is the source of truth: `"hour"` = hourly rate, `"annum"` = annual salary, `"day"` = daily rate, `"week"` = weekly. The `min`/`max` numbers are in the unit indicated by `period`. For a hospitality dataset analysis, group by `period` first.

**Does this actor return chef-specific roles only?**
No — Caterer.com covers all hospitality verticals: kitchen (chefs, kitchen porter, sous-chef), front-of-house (waitstaff, host, sommelier), management (restaurant manager, GM, F\&B), events (event coordinator, banquet manager), hotel-specific (front desk, housekeeping, concierge), and adjacent roles (bar staff, pastry, butcher). Add `?what={role}` to the query string for narrower keyword filtering.

**What does each dataset-item charge cover?**
One hospitality job row with all 14 JSON-LD fields plus the structured salary band (with `period` correctly identifying hourly vs annual) and structured location (lat/lng). `maxItems` is per-listing-URL.

### Support

- **Bugs / feature requests** — open an issue on the GitHub repo
- **Custom exports / tailored fields** — drop a note via the Apify Store contact form
- **Other actors** — see my [Apify Store profile](https://apify.com/memo23)

***

### 🤖 For AI Agents & LLM Apps

Compact reference for AI agents calling this actor via the [Apify MCP server](https://mcp.apify.com) or the Apify API (actor: `memo23/caterer-scraper`).

**Purpose:** Scrape UK hospitality job postings from Caterer.com — one flat row per job with the full JobPosting JSON-LD, a structured salary band (often hourly), lat/lng, and a populated applyUrl on direct-apply roles.

**Minimal input:**

```json
{
  "startUrls": ["https://www.caterer.com/jobs/in-london"],
  "maxItems": 25,
  "maxConcurrency": 4,
  "maxRequestRetries": 6,
  "enrichEmails": false,
  "qualifyByPayment": false
}
```

Listing URLs (`/jobs/in-london`, `/jobs/chef/in-manchester`, with optional `?postedWithin` / `?companytypes` / `?salary` / `?jobType` filters) auto-paginate; direct detail URLs (`/job/{slug}-job{id}`) emit one row each.

**Output:** one row per job (`rowType: "job"`) — sourceSearchUrl, jobId, jobUrl, sourceSite, title, description, datePosted, validThrough, employmentType, industry, directApply, jobLocationType, applicantLocationRequirements, employer {name, url, logoUrl}, location {text, locality, region, postalCode, country, lat, lng}, salary {rawText, min, max, currency, period}, applyUrl, applyType, scrapedAt.

**Behaviors an agent should know:**

- `maxItems` is per listing URL (not global) — 3 listings at `maxItems: 100` can yield 300 rows; direct detail URLs always emit 1 row. Default 1000; free tier is capped at 100 total.
- Result set is scoped server-side to the hospitality vertical; add `?what={role}` to narrow by keyword.
- `enrichEmails` (opt-in) adds contactEmail + contactWebsite and is billed per email found, only on a hit; `qualifyByPayment` requires `enrichEmails` and adds no extra charge.
- Apify Residential GB is used (built-in) for the per-job detail fetch — leave `proxy` empty unless supplying your own.
- Billing: one charge per dataset item (job row), plus per-email charges only when `enrichEmails` returns a match.

***

### ⚠️ Disclaimer

This Actor is an independent tool and is **not affiliated with, endorsed by, or sponsored by** Caterer.com or any of its parent / sister companies. All trademarks mentioned are the property of their respective owners.

The scraper extracts only **publicly visible** hospitality job postings from Caterer.com — no login, no CAPTCHA solving, no credential forgery. The actor uses a conservative concurrency cap (default 4 parallel requests) to avoid burdening Caterer's infrastructure.

Users are responsible for:

- Complying with Caterer.com's Terms of Service
- Following UK GDPR + your jurisdiction's data-protection laws when storing or processing scraped postings
- Not contacting candidates listed by employers in scraped postings
- Not republishing scraped data in a way that competes commercially with Caterer.com

***

### SEO Keywords

caterer scraper, caterer.com scraper, scrape caterer, hospitality jobs scraper uk, chef jobs scraper, restaurant jobs scraper, hotel jobs scraper, uk hospitality jobs api, hospitality recruitment data, chef recruitment uk, hotel staff recruitment, kitchen jobs api, uk hospitality salary data, hourly salary scraper, hospitality market intelligence, chef salary benchmark uk, restaurant manager salary uk, hotel salary data uk, sous chef scraper, commis chef scraper, london hospitality jobs, manchester hospitality jobs, edinburgh hospitality jobs

# Actor input Schema

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

Mix of listing URLs (e.g. `https://www.caterer.com/jobs/in-london`, `https://www.caterer.com/jobs/chef/in-manchester`) and direct job-detail URLs. Filters supported in the query string: `?postedWithin=1|3|7|14`, `?companytypes=1|2`, `?salary={int}`, `?jobType=permanent|contract|temporary|partTime|workFromHome`. Listings auto-paginate; details emit one row each. Result set is scoped server-side to the hospitality vertical (chef / restaurant / hotel / events) — exactly what caterer.com's web search shows. Both plain URL strings and the request-list object form (`{"url": "https://.../"}`) are accepted.

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

Maximum job rows emitted **per listing URL**. Pass 3 listings with `maxItems: 100` → up to 300 total rows (100 each). Direct detail URLs always emit 1 row each. Each row is one paid dataset item. Default 1000. Free-tier users are additionally capped at 100 total rows.

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

Parallel HTTP requests for detail-page fetches. Concurrency 3-5 is the sweet spot via Apify Residential GB.

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

Per-URL retry budget on network errors, proxy CONNECT failures, HTTP/2 stream resets, and transient 4xx responses. Each retry rotates the proxy session. Default 6.

## `enrichEmails` (type: `boolean`):

If enabled, finds a contact email for each result from its own website (or by discovering it from the name). Adds contactEmail + contactWebsite columns plus a detailed emailEnrichment object. Billed per contact email found; only charged when an email is returned, never for misses.

## `qualifyByPayment` (type: `boolean`):

Requires "Enrich with contact emails". Scans each business's website — reusing the pages already fetched for email discovery, so no extra cost or time — for payment processors and e-commerce platforms (Stripe, Shopify, PayPal, Paddle, Lemon Squeezy, WooCommerce, Square, Chargebee and more). Adds takesPayments (is this a real paying business?), paymentProcessors (which stack), stripeLiveKey (the public key if exposed) and paymentConfidence. Turn raw contacts into monetization-qualified leads. No extra charge — included with each enriched company.

## `proxy` (type: `object`):

Leave empty — the actor already routes all traffic through its own built-in residential proxy at no extra cost to you. Only set this if you want to use your own proxies.

## Actor input object example

```json
{
  "startUrls": [
    "https://www.caterer.com/jobs/in-london"
  ],
  "maxItems": 1000,
  "maxConcurrency": 4,
  "maxRequestRetries": 6,
  "enrichEmails": false,
  "qualifyByPayment": false
}
```

# 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 = {
    "startUrls": [
        "https://www.caterer.com/jobs/in-london"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("memo23/caterer-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 = { "startUrls": ["https://www.caterer.com/jobs/in-london"] }

# Run the Actor and wait for it to finish
run = client.actor("memo23/caterer-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 '{
  "startUrls": [
    "https://www.caterer.com/jobs/in-london"
  ]
}' |
apify call memo23/caterer-scraper --silent --output-dataset

```

## MCP server setup

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