Caterer.com Scraper at a glance
Caterer.com Scraper is a ready-to-run Apify actor from abotapi for collecting jobs data. Its documented output includes job id, change type (incremental mode), title, employer and location, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.20 per 1,000 results on the Apify Free plan and from $1.00 on paid plans, with smaller per-run or optional feature charges listed on Apify.
- Runs on
- Apify cloud: console, API, schedules and integrations
- Data type
- Jobs, Automation, Developer Tools
- Pricing
- $2.20 per 1,000 results (Free plan), from $1.00 on paid plans
- Output
- Documented below · JSON, CSV, Excel
- Inputs
- 21 options
Scrape UK hospitality jobs from Caterer.com, including chef, hotel, restaurant, bar, and events roles. Search by keyword, location, filters, or URLs. Returns salary, employer, logo, location, skills, and 35+ fields, with optional full description, GPS, and company profile.
What Caterer.com Scraper can do
- 35+ fields per job from the listing page alone. No detail fetch required for title, parsed salary, employer, logo, location, posting source, skills, and snippet.
- Two ways to run. Build a search from keyword, location, and filters, or paste any Caterer.com search URL and walk it forward.
- Real server-side filters. Job type, advertiser type (direct employer vs agency), minimum salary by period (year, day, or hour), posted-within window, and sort order.
- Parsed salary. The free-text salary string is split into min, max, currency, and period, including the hourly rates common in hospitality.
- Optional full details. GPS coordinates, structured address, full description, employment type, valid-through date, and company profile, plus any contact number or email the posting itself publishes.
- Cost control built in. A single job cap, an optional page cap, and a residential request budget to bound what each run collects and spends.
Choose what to collect
These inputs let you configure Caterer.com Scraper - UK Hospitality Jobs, Salaries & Details. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
modestring · required | How to find jobs: build a search from filters, or paginate URLs you paste. |
locationsarray | Towns, cities, counties, or regions (Search mode). Examples: 'London', 'Manchester', 'Edinburgh', 'Surrey'. One search runs per location. Leave empty for all of the UK. |
keywordsstring | Hospitality role, skill, or employer to search for. Example: 'chef', 'sous chef', 'restaurant manager', 'bartender'. Leave empty to list all hospitality jobs in the location. |
jobTypestring | Contract / working arrangement filter. |
companyTypestring | Restrict to direct employers or recruitment agencies. |
minSalaryinteger | Lowest salary to include. Combined with the salary period below. Many hospitality roles quote an hourly rate, so set the period to match. Leave empty for no minimum. |
salaryTypestring | Unit for the minimum salary filter. |
Show 14 more inputs
| Input | What it controls |
|---|---|
postedWithinstring | Only jobs posted within this many days. Leave as Any time for no date filter. |
sortBystring | Result ordering. |
urlsarray | Caterer.com URLs to scrape (URL mode). Accepts listing pages (location, county, keyword, job type, filters?page=N) and single job pages. Filter fields above are ignored. A page number in the URL is honoured as the starting point. Left untouched, one example of each URL shape is scraped. |
maxListingsinteger | Total jobs to collect across all searches. This is the main limit. Set 0 for unlimited (bounded by Max pages). Values above 1000000 are capped at 1000000. |
maxPagesinteger | Optional safety limit on pages walked per location/URL (25 jobs per page). Leave at 0 to walk the whole catalogue: the run stops at Max jobs, the site's own last page, or a repeat-page guard, not an artificial page cap. |
resumeFromRunIdstring | Optional. ID of a previous run of this actor (or a dataset ID). Jobs already in that dataset are skipped, so this run returns only NEW jobs (a delta). Combine both runs' datasets for the full set. Max jobs then counts only the new jobs. For recurring daily monitoring of the same search, use Incremental mode below instead. |
incrementalModeboolean | Turn this on for daily or recurring monitoring. The first run returns all matching jobs as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED jobs. A job is UPDATED when any of its returned fields changes (title, salary, location, employer, description, dates and so on; the changed field names are listed in changedFields). Excluded from the comparison: scrapedAt, detailFetched, crossPostedCount, sourceSearchUrl, searchKeyword, searchLocation and the ad-placement flags isSponsored, isHighlighted, isTopJob, isTrafficFromPartner, plus anything you list in \"Ignore fields\" below. Turn on \"Emit unchanged\" or \"Emit expired\" only when you also want those jobs returned (and billed). State is kept separately for each distinct search/filter setup (or by State key below). |
stateKeystring | Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from your search/filter settings, different searches then never mix state with each other. |
emitUnchangedboolean | Off by default. Turn on to also return jobs that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want the full snapshot every run. |
emitExpiredboolean | Off by default. Turn on to also return jobs that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search, not when Max jobs or Max pages capped it, or when Resume was used. This returns, and bills, extra synthetic rows. |
ignoreFieldsForChangesarray | Optional. Field names that must NOT make a job count as UPDATED, for example salary.max or employer.name. Nested fields use dot notation. The fields are still returned in the output, they are just not compared. Already ignored by default: scrapedAt, detailFetched, crossPostedCount, sourceSearchUrl, searchKeyword, searchLocation, isSponsored, isHighlighted, isTopJob, isTrafficFromPartner. |
mcpConnectorsarray | Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON, the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com). |
notionParentPageUrlstring | URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors. |
maxNotifyListingsinteger | Cap on items written to each connector per run. Does not affect the dataset. |
Fields in the output
The documented dataset includes the fields below. Availability can depend on the source page and selected mode.
jobIdJob ID (text)changeTypeChange type (incremental mode) (text)titleTitle (text)employerEmployer (object)locationLocation (object)salarySalary (object)datePostedPosted (text)sourceSiteSource (text)jobUrlURL (link)changedFieldsChanged fields (incremental mode) (array)firstSeenAtFirst seen (incremental mode) (date)lastSeenAtLast seen (incremental mode) (date)Show 9 more fields
employmentTypeEmployment (array)industryIndustry (text)jobLocationTypeWork type (text)validThroughValid through (text)applyTypeApply (text)contactPhonesContact phones (array)contactEmailsContact emails (array)descriptionTextDescription (text)companyCompany (object)Example output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"rowType": "job",
"scrapedAt": "2026-01-01T00:00:00.000Z",
"jobId": 100000001,
"jobUrl": "https://www.caterer.com/job/head-chef/sample-agency-job100000001",
"applyUrl": "https://www.caterer.com/job/head-chef/sample-agency-job100000001",
"sourceSite": "Caterer.com",
"title": "Head Chef",
"datePosted": "2026-01-01T00:00:00.000Z",
"employer": {
"id": 1000000,
"name": "Sample Restaurant Group",
"url": "https://www.caterer.com/jobs/sample-restaurant-group?cmpId=1000000",
"logoUrl": "https://www.caterer.com/CompanyLogos/00000000000000000000000000000000.png",
"isAnonymous": false
},
"location": {
"text": "Soho, Central London (W1)",
"postalCode": "W1",
"locality": "Soho",
"region": "London",
"country": "GB",
"latitude": 51.5,
"longitude": -0.13
},
"salary": {
"rawText": "From £14 to £18 per hour",
"min": 14,
"max": 18,
"currency": "GBP",
"period": "hour"
},
"skills": [
"Menu planning",
"Food safety"
],
"textSnippet": "We are looking for an experienced head chef to lead our kitchen team.",
"isSponsored": false,
"crossPostedCount": 1,
"description": "Full job description text appears here when fetchDetails is enabled.",
"employmentType": [
"FULL_TIME"
],
"industry": "Catering, Catering-Chef",
"validThrough": "2026-02-01T00:00:00.000Z",
"directApply": true,
"applyType": "DirectApply",
"contactPhones": [],
"contactEmails": [],
"company": {
"name": "Sample Restaurant Group",
"size": "51-200",
"founded": 2005,
"industries": [
"Hospitality"
]
},
"detailFetched": true
}Ways to use this data
- Recruitment and staffing agencies: benchmark competitor postings, salary bands, and hiring volume across chef, front-of-house, and management roles.
- Job board and career site operators: mirror UK hospitality vacancies with structured salary, location, and employer data for your own listings.
- Compensation and labour-market research: track parsed hourly and annual pay ranges by role, region, and posting date to study wage trends in hospitality.
- Employer brand and competitor monitoring: watch specific companies' hiring activity, job counts, and posting frequency over time.
- Sales lead generation: find companies actively hiring chefs, managers, or bar staff as leads for recruitment or hospitality-supply sales.
Before you run
Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.
Questions about this actor
What data does Caterer.com Scraper return?
The documented output for Caterer.com Scraper includes job id, change type (incremental mode), title, employer, location, salary, posted and source. Availability of each field depends on the source page and the selected mode.
How much does Caterer.com Scraper cost?
It costs $2.20 per 1,000 results on the Apify Free plan and from $1.00 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.
Can I get only new jobs on a schedule?
Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated jobs, and unchanged ones are not billed. Turn on Emit expired jobs only if you also want to know when a tracked job disappears, and note that an EXPIRED batch on a large campaign is not capped by Max jobs.
Why did my run return few or no results?
Check that your filters aren't too narrow, and that the connection settings match the Plan Requirement section above. A run that could not read any pages at all fails with a clear message instead of returning an empty dataset, so "no jobs match" is never confused with "nothing could be read".
Does this actor collect personal candidate information?
No. It collects job postings, which employers and agencies publish to attract applicants, not candidate or worker data. With Fetch full job details on, it also best-effort harvests any contact number or email the posting itself publishes (a tel:/mailto: link on the job page, or a number or address typed into the description), and it is frequently empty. This is usually a company or agency line, but it can be a named recruiter's direct number or email, which may count as personal data under UK GDPR, so handle these two fields accordingly.
Can I use it with AI agents or MCP?
Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear, or Airtable.
