Vivino Wine Data Scraper: ratings, prices & taste profiles
Pricing
from $2.00 / 1,000 wine result extracteds
Extract wine ratings, prices, taste profiles, reviews, and grape varieties from Vivino. Search by wine name or URL. Fast HTTP-only approach with no browser needed. Export JSON, CSV, or Excel.
All notable changes to Vivino Wine Data Scraper are documented here.
Chateau Margaux had its chateau prefix stripped, then the residual margaux was used as a fallback winery slug - which on Vivino resolves to an unrelated winery whose explore matches passed the relevance probe by sharing only chateau and margaux words with the query.REGION_NAMES_BLOCKLIST in src/constants.ts: lowercase, accent-stripped region names that must not be used as winery-slug fallbacks. Expandable on observation of similar false-positives.min(2, qw.length) as the per-match threshold instead of a hard-coded >= 2. Previously, when buildQueryWords returned a single distinctive word (e.g. "Chateau Margaux" -> qw = ['margaux'] because chateau is filtered as a WINERY_PREFIX stop word), the probe was mathematically impossible to pass, so the correct winery slug (chateau-margaux -> winery 1319) was rejected and the actor fell through to Strategy 2, which surfaced "Andrena Margaux" (winery "Château Le Coteau") as the documented false positive. The relaxed threshold allows single-word matches to land on the right producer while keeping the protective behavior for multi-word queries (e.g. the T12 "Jean Other Specific Cuvee" path still requires 2/4 matching words).Sprint 6.1: fix last-run-summary.output.charged observability counter.
pushDataAndCharge (apify/dist/charging.js:407-412) auto-schedules BOTH the explicit event (wine-result) AND the synthetic apify-default-dataset-item event when pushing to the default dataset. mergeChargeResults sums chargedCount across both. So every successful Actor.pushData(item, 'wine-result') returned chargedCount = 2 (1 wine-result + 1 synthetic). The pre-fix counter accumulated raw chargedCount, producing charged = pushed * 2 on every run.src/run.ts:336 now collapses chargedCount > 0 to a +1 increment. This restores the original observability intent (track "rows actually billed" for revenue-leak detection — Sprint 5 goal) by ignoring the synthetic dataset event.charging.js:290-294 skips apify- synthetic events). Only wine-result × $0.003 was ever charged.chargedCount = 2 each, summary showed charged: 20. After fix the same scenario will report charged: 10.chargedCount = 2 per call and asserts charged === pushed).Sprint 6 of the post-audit roadmap: Penfolds Grange Strategy 2 deep-dive. Closes a known parity gap where the user query "Penfolds Grange Bin 95 Shiraz" produced a wrong-wine row (Bin 128 Shiraz) instead of the correct Penfolds Grange.
Penfolds Grange correctly surfaces Grange (wineId 1136930).candidateMatchesQueryCuvee(name, winery, query) in scoring.ts - softer than distinctiveWordsFilter, asserts only that the user query's first distinctive word (the cuvee kernel, e.g., 'grange') appears in the candidate's name. Used to reject candidates that pass score thresholds but miss the cuvee.processWineEntries on search-page entries) now runs the cuvee check on its top result. Candidates that fail fall through to Strategy 2.3 instead of being emitted as wrong-wine rows._strategy value s2-shortened for rows surfaced via Strategy 2.3; counted in last-run-summary.output.strategies and in the Strategy 2 fallback aggregate.candidateMatchesQueryCuvee + 2 covering Strategy 2.3 behavior end-to-end).Sprint 5 of the post-audit roadmap: schema-level cleanups + observability honesty.
_strategy diagnostic field stripped from every public dataset row at push time (was previously emitted but undeclared in dataset_schema.json). The aggregate strategy distribution stays available in last-run-summary.output.strategies.last-run-summary now distinguish pushed (rows in the dataset) from charged (rows successfully billed via PPE). On runs with zero charge failures these two numbers are identical; when they diverge it is a real revenue-leak signal worth investigating.dataset_schema.json:fields now declares nullable types (["string","null"] etc.) for every field that the runtime can actually emit as null (winery, vivino_url, appellation, average_rating, price, alcohol, image_url, wineId, vintageId, inputSource, shipTo, vintage, wine_description, taste_profile, reviews, searchQuery). Clients that validate the schema against the rows no longer get type-mismatch warnings.key_value_store_schema.json now embeds a full jsonSchema for the last-run-summary blob so the Apify Console auto-documents the structure and any future shape drift in the code is caught.Sprint 4 of the post-audit roadmap: observability + documentation.
last-run-summary at the end of every run. Captures timing, input shape, strategy distribution, cache stats, and resilience counters. Useful for offline drift detection and capacity planning.key_value_store_schema.json declares the last-run-summary collection so the Apify Console surfaces it next to OUTPUT.error / errorMessage fields, the diagnostic _strategy field, and the Key-Value Store run summary. Includes a sample error row and a sample summary blob.Note: adoption of the speculative /api/wines/{id} JSON endpoint (originally on the Sprint 4 plan) was deferred to a dedicated research sprint - the endpoint shape needs validation against the live Vivino API with debug-tagged probes before going to production.
Sprint 3 of the post-audit roadmap.
Actor.pushData(item, 'wine-result') shortcut (Apify v3.4+). Closes the brief push-without-charge gap that existed when push and charge were separate calls.WINERY_SUFFIXES constant out of the per-entry loop in processWineEntries.exploreToScrapedWine export and its 11 tests; deleted the unused SearchPageResult interface.scripts/canary-vivino.sh runs the live Actor against a 3-wine canary input (one per strategy) and asserts that core fields are still present. Designed to be wired as a daily Apify scheduled task for early detection of Vivino API/HTML drift.Sprint 2 of the post-audit roadmap: Phase 4 hygiene + 2 quality fixes + diagnostic field.
NODE_ENV=production and uses npm ci against a committed package-lock.json (reproducible installs).actor.json metadata updated post TypeScript migration (templateId is now ts-empty, minMemoryMbytes bumped from 128 to 256 for Node 22 + cheerio reliability, defaultRunOptions now pins build: latest and memoryMbytes: 512).searchQuery, inputSource, error, errorMessage, scrapedAt.winery now returns null (instead of the placeholder 'Unknown') when extraction fails on a successful row. This restores parity with the JS monolith and stops the downstream quality filter from treating 'Unknown' as a real producer name. Error rows still use 'Unknown' for display._strategy field (url, s1, s2-discovered-slug, s2-entries, error) so operators can trace which code path produced each result. Diagnostic-only - safe to ignore in client integrations._strategy smoke).Post-promotion hotfix surfaced by the 5-audit batch (apify-scraper-builder + apify-monetization-expert + scraper-audit-expert + scraping-expert + code-reviewer + code-simplifier).
_food_pairings private taste-profile field no longer leaks into the public dataset; it is now stripped after enrichment.food_pairings correctly backfills from the taste profile when the API result lacked it (parity with the JS monolith).taste_profile and reviews are now omitted from the dataset row when the user opts out (previously shipped as explicit null).searchMode: name_only now actually disables vintage extraction (previously declared in the input schema but ignored by the code).wineNames and wineUrls legacy fields are now declared in the input schema (still merged with wines at runtime).WINERY_PREFIXES, stripAccents) now imported from the canonical modules.htmlToScrapedWine accepts a fallbackName option, removing post-construction mutation in processWineEntries.extractMaxFloat and extractMaxInt consolidated into a single generic extractMax helper.Full TypeScript rewrite preserving the original scraping methodology.
average_rating is no longer silently 0 when Vivino has rated the wine. The HTML rating extractor was looking for a field name (average_rating) that Vivino does not use in its inline data; the actual field is ratings_average (plus wine_ratings_average for wine-level fallback). When extraction failed, the output reported average_rating: 0 together with a non-zero ratings_count, suggesting a real "zero star" rating that did not exist. The scraper now scans the correct field names (with the legacy spelling as a last-chance fallback) and prefers wine-level rating when the vintage-level rating is unavailable. Fields with no rating data return average_rating: null so consumers can distinguish "unrated" from "actually zero".NSG, Gds, VV, BLC, RGE, 1er, P.C., G.C., CDP, CDR, SGN, VT, MC (monopole) are expanded to their full form (Nuits-Saint-Georges, Grandes, Vieilles Vignes, Blanc, Rouge, Premier, Premier Cru, Grand Cru, Chateauneuf-du-Pape, Cotes du Rhone, Selection de Grains Nobles, Vendanges Tardives, Monopole) so the quality filter recognizes them in Vivino result names. Recovers previously-rejected wines such as Mugneret Gerard NSG Aux Cras (now matches Nuits-Saint-Georges 1er Cru 'Aux Cras').AOC, AOP, IGP, VDF, VDP, DOC, IGT, and others) and 4-digit years are now stripped from the search query. They are derived from the vintage field already, so leaving them in the search text just polluted Vivino's matcher and confused the quality filter into rejecting good results. Knock-on effect: previously-rejected wines like Clos de la Hutte (Thibaud Boudignon Savennières) and Marc Kreydenweiss Clos du Val D'Eléon should now match.Fils, Fille, Frères, Père) are now treated as non-distinctive when comparing the query against a match. This stops false rejections on wines like Boulard & Fille Les Murgiers and Dehours & Fils Grande Réserve.Champagne Blanc., L'Alsace., La Corse., Le Rhône Septentrional., La Côte Chalonnaise et le Mâconnais. — have that prefix removed automatically. The remaining text is what gets searched on Vivino, so the producer and wine name become the leading tokens (e.g. Franck Pascal Fluence Brut Nature instead of Champagne Blanc. S.A. Franck Pascal "Fluence" Brut Nature 50). Substantially improves match rate on wine-list-style catalog exports.Champagne Blanc. S.A. Franck Pascal "Fluence" Brut Nature 50<TAB>NV) are now parsed correctly: the description column is used as the search query, the vintage column accepts both years and NV, and stray catalog elements are stripped before searching: curly quotes (""''), legal-entity markers (S.A., SCEA, SARL, SAS, EARL, GAEC`), and a trailing price.Jean-Claude Bachelet, Chassagne-Montrachet, La Boudriotte Rouge, the scraper could previously return a wine from Jean-Claude Ramonet because the first two words ("jean", "claude") matched. The validator now also requires the producer's family name (last significant word in the winery) to appear in the query.Domaine des Comtes Lafon, Meursault Premier Cru, Charmes) are now correctly tokenized, restoring matches that were previously rejected by the validator due to trailing characters attached to words. Expected effect: significantly higher extraction success rate on real catalog inputs.winery field, which also disabled the downstream quality filter and let unrelated wines be returned. The filter now activates correctly on these cases and rejects results whose distinctive query words do not appear in the matched wine. Side effect: fewer null prices in the output, since most of the missing prices came from these mismatched results.ACTOR_MAX_TOTAL_CHARGE_USD setting users can configure in Run options to cap per-run spending.error and errorMessage dataset fields documented as null on success.wines field prefill in the Console form now showcases the 6 accepted input shapes pedagogically: wine name only, name with vintage, Vivino URL (canonical), Vivino URL with ?year= parameter, scheme-less Vivino URL (auto-prefixed with https://), and Vivino URL with locale path (/fr/). Helps users discover the breadth of accepted formats without reading the docs.wineUrls + wineNames with a single wines array that auto-routes URLs and names by shape. Mix freely; the actor handles routing.maxResultsPerSearch (now hardcoded to 1 -- best match only) and proxyConfig (was unused).sectionCaption/sectionDescription keys. All inputs are visible without expanding sections.wineUrls and wineNames keys still work silently. Existing scheduled tasks and API integrations continue running without change. No deprecation warning.## Is it legal to scrape Vivino? canonical H2 (hiQ Labs reference, GDPR caveat for EU review data, Apify blog link)## Support & feedback closing block at end of README with Issues tab linkactor.json title, and seoTitle (was 3 different forms)seoTitle$49/month → $29/month (~9,600 wines/month)console.apify.com/settings/integrations now includes ?fpr=mrbridgeetc. from L49 wine-type listing and from dataset_schema.json wine_type descriptionPromise.all with Promise.allSettled in dual-search (with/without shipTo) and enrichment (taste+reviews) so a transient Vivino failure on one fetch no longer drops the whole wine. Charge errors now logged as warnings with a per-run counter exposed in the final status message (silent revenue loss becomes observable).reviews field omitted when includeReviews: false, taste_profile and food_pairings omitted when includeTasteProfile: false. Eliminates empty columns in exported data.fetchHtml), global rate limit cooldown shared across all concurrent requests, break winery slug loop on persistent 429. Fixes large batch runs (34+ wines) where queries 26+ failed due to Vivino rate limiting (29/34 vs 18/34 without fix).maxResultsPerSearch from 5 to 1 (best match only). Users pay per result, so default should minimize cost; set higher explicitly for alternatives.maxResults alias takes priority over schema default + slice results after double-search merge.?year=XXXX) + carry explore API prices through wineEntries fallback (HTML pages often lack pricing in JSON-LD).Initial release with wine name search, URL scraping and pay-per-event pricing; winery strategy with matching/scoring improvements; streaming architecture; rate limit handling; shipTo support; localization dropdowns; OOM fixes; food pairings, description and alcohol fields; code refactoring.