Fresha Scraper - Salons, Spas, Services & Reviews
Pricing
from $1.00 / 1,000 listing records
Scrape Fresha salon and spa listings: business profiles, service menus with prices and durations, opening hours, team members, photos, ratings and client reviews. Search by keyword and location or paste venue and professional links. Resume, incremental updates and MCP export included.
SEARCH scrapes Fresha listings for a keyword and location. LISTING_URLS scrapes the exact venue pages (fresha.com/a/...) and professional profiles (fresha.com/p/...) you paste.
Service or business keyword, e.g. hair, massage, nails, barber, facial, tattoo. Used in SEARCH mode.
City or area name, e.g. Sydney, London, New York. Resolved automatically to map coordinates. Leave blank when latitude/longitude or a venue URL list is provided.
Optional map latitude. When set together with longitude it overrides the resolved Location.
Optional map longitude. When set together with latitude it overrides the resolved Location.
How many result pages (20 listings each) to walk per search. Leave blank or 0 for unlimited until Max items is reached.
Ordering of search results. RATING and DISTANCE are narrowed assertions: results come back in that order.
Optional minimum service price filter in the local currency of the search area.
Optional maximum service price filter in the local currency of the search area.
Return only venues currently running deals or offers.
Return only venues offering group appointments or classes.
Return only venues carrying the Fresha Verified badge.
Only venues with bookable availability on this date (YYYY-MM-DD). Used in SEARCH mode.
Fresha URLs to scrape in LISTING_URLS mode. Supported shapes, which can be mixed freely: venue pages (fresha.com/a/...), professional profiles (fresha.com/p/...), SEO landing pages (fresha.com/lp/..., harvested for the venue links they contain), localized venue links in the short locale form (e.g. fresha.com/de/a/...), and venue links carrying tracking parameters (?utm_source=..., fbclid=... — matched the same as clean venue links). Book-now links (fresha.com/book-now/...) also resolve to their venue when encountered. The URL mode is selected by Mode above.
[ { "url": "https://www.fresha.com/a/rachel-french-hairdresser-sydney-24-30-springfield-avenue-u0by2m6f" }, { "url": "https://www.fresha.com/p/suha-alsayah-5784524" }, { "url": "https://www.fresha.com/lp/en/bt/spas/in/au-sydney" }, { "url": "https://www.fresha.com/de/a/rachel-french-hairdresser-sydney-24-30-springfield-avenue-u0by2m6f" }]Fetch each listing's full profile: description, contact number, opening hours, service menu with prices and durations, packages, team members, photo gallery, Instagram, amenities and review highlights. Adds the detail-enrichment charge per listing. Without it you still get the listing card: name, rating, review count, badges, address, geo and photos.
Attach client reviews to each listing: rating, text, date, author, salon reply and review photos, plus the 1-5 star distribution. Adds the review-enrichment charge per listing. First page is included; deeper pages are walked automatically.
Stop collecting reviews for a listing after this many. 0 means no limit (walk every available page).
Order in which reviews are collected.
Stop after this many listing records (reviews attached to a record do not count as items). Run stops gracefully at the cap.
Datacenter proxies are the default and work on every plan (measured working on every endpoint of this site). Residential proxies are recommended for the most reliable results on large or frequent runs. If the connection is refused, the actor escalates automatically through backup connections, including residential ones; that residential traffic is billed to your Apify plan when it engages. The run always uses a proxy unless you explicitly turn it off here or supply your own proxy URLs.
{ "useApifyProxy": true}ID of an interrupted run to continue. The run picks up after the last listing already saved and reuses its key-value state. Leave empty for a fresh run.
Compare listings against the previous run for the same scope (state key) and only emit NEW or UPDATED rows (plus optional EXPIRED tombstones). Unchanged listings are skipped and not charged. A listing previously marked EXPIRED that is found again is emitted as REAPPEARED with its original firstSeenAt. What drives UPDATED: every emitted listing field except the exclusions below and run bookkeeping (scrapedAt, changeType, changedFields, firstSeenAt, lastSeenAt) - e.g. the services menu (names, prices, durations), rating, reviewsCount, address and coordinates, images, amenities, social links. Never compared, so they never mark a row UPDATED on their own (they rotate or change on their own without the listing changing): portfolioImages, recentReviewers, openingStatus, openingStatusDetails, closed, workingHours, instagramMediaCount, groupingScore, topReviewedServices, reviewTeamMembers. Review order is ignored too: reviews are compared as an orderless set of id, rating, text, date and reply. Extend the exclusions with ignoreFieldsForChanges.
Name of the remembered baseline for incremental mode. Defaults to a hash of the current scope (mode, query, location, URL set), so two runs with the same settings compare against each other automatically. Change it to track a different baseline.
In incremental mode, also emit rows classified UNCHANGED (handy for full snapshots or debugging). Unchanged rows still carry changeType so you can filter.
In incremental mode, emit an EXPIRED row for listings present in the baseline but missing from this run. Tombstones respect Max items.
Extra dataset fields that must NOT mark a record UPDATED when they change (rotation noise like image CDNs). Sensible defaults are built in; anything added here is appended.
Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify → Settings → API & Integrations, then select it here. Notion gets a rich page-per-item export; other connectors get a best-effort write/digest. Leave empty to skip; never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
[]URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.