Vivino Scraper
Pricing
from $1.80 / 1,000 results
Vivino Scraper
[π° $1.80 / 1K] Extract structured wine data from Vivino: name, winery, vintage, region, grapes, community ratings with counts, price, taste profile, food pairings, and optional reviews. Search by keyword or paste wine URLs. 23 countries, 15 currencies.
Pricing
from $1.80 / 1,000 results
Rating
0.0
(0)
Developer
SolidCode
Maintained by CommunityActor stats
0
Bookmarked
11
Total users
0
Monthly active users
15 days ago
Last modified
Categories
Share
Pull structured wine data from Vivino at scale β winery, vintage, region, grape varieties, community ratings with the rating counts behind them, market prices, taste-profile scores, food pairings, and opt-in reviews. Search by wine name or paste Vivino URLs directly, and localize prices across 23 countries and 15 currencies. Built for wine retailers, sommeliers, market researchers, and catalog teams who need clean, comparable wine data without copying it bottle by bottle from Vivino.
Why This Scraper?
- Know whether a rating is really that vintage's own β the
ratingIsWineLevelfield separates three cases no other Vivino extractor exposes: the vintage's own score, the wine's overall score standing in, and a bottle rated too few times for Vivino to publish any score. About two rows in five carry the flag, so filtering on it changes your sample materially. - Invented vintages are filtered out β Vivino's index lists release years a producer never actually bottled, each wearing a copied rating. Removing them cut phantom rows on an all-vintages sweep from 82% to 0% and lifted price coverage on that same sweep from 18% to 70%.
- Alcohol content on nearly nine bottles in ten β ABV lands on 88.9% of wines measured across 1,527 rows, alongside region and country on 100% and grape varieties on 95%.
- Non-vintage wines are labelled, not left blank β a Champagne, Cava, or NV blend returns the literal
"N.V."invintage(58% of rows on a Champagne run), so "no year exists" is never confused with "the year failed to read". - Paste back any URL the scraper produced and get a full record β Vivino serves a wine page in three different shapes and all three resolve to a complete detail parse, taking the output-to-input round trip from 15% to 100% of URLs.
- Up to 100 community reviews per wine β reviewer username, their own rating, the full comment text, and the review date, each emitted as its own row for easy analysis.
- Localized pricing across 23 countries and 15 currencies β quote in USD, GBP, EUR, CHF, AUD, JPY, and more to match the market you actually sell into.
- Sweep every vintage of a wine, or pin to one exact year β "Ignore vintage" returns all release years for price-over-time work; "Match exact vintage" locks to the year you typed and holds it on 100% of returned rows.
- Taste-profile scores plus the community's dominant flavor notes β body, acidity, tannins, sweetness, and fizziness on the axes Vivino measures for that wine type, with flavor-note groups ranked by how strongly tasters called them.
Use Cases
Wine Retail & Pricing
- Monitor competitor and market pricing on the same wine across countries
- Track a vintage's price as it moves from current release to back-vintage
- Spot under-rated, well-priced bottles by comparing rating to price
- Validate landed costs against local market currency before importing
Restaurants & Sommeliers
- Build a by-the-glass and bottle list ranked by community rating
- Match wines to menu courses using the food-pairing fields
- Surface crowd-pleasers with high ratings and high rating counts
- Find structurally similar alternatives using body, acidity, and tannin scores
Market Research & Trends
- Track how a region or grape variety is rated across thousands of wines
- Benchmark a producer's portfolio against its peers
- Analyze taste-profile trends by region, country, or vintage year
- Quantify community sentiment from review text and ratings
App & Catalog Building
- Enrich an e-commerce wine catalog with ratings, images, and tasting notes
- Power a wine-recommendation engine with taste-profile vectors
- Populate a wine app with structured pairings, grapes, and ABV
- Fill gaps in a product database using direct Vivino URL lookups
Getting Started
Search by Wine Name
The simplest run β one query, full taste profile on by default:
{"searchQueries": ["Barolo"],"maxResults": 50}
Track Every Vintage of a Wine
Strip the vintage to gather all release years of a single wine, priced in euros:
{"searchQueries": ["Tignanello"],"vintageHandling": "name_only","countryCode": "FR","currencyCode": "EUR","maxResults": 100}
Pull a Wine With Community Reviews
Look up specific bottles by URL and collect up to 25 reviews each:
{"startUrls": ["https://www.vivino.com/en/tignanello/w/1652"],"includeReviews": true,"maxReviewsPerWine": 25}
Full-Featured Example
Mix queries and URLs, exact vintage matching, reviews on, localized to the UK:
{"searchQueries": ["Penfolds Grange 2017", "Napa Cabernet Sauvignon"],"startUrls": ["https://www.vivino.com/en/grange/w/1136930"],"vintageHandling": "name_and_vintage","includeTasteProfile": true,"includeReviews": true,"maxReviewsPerWine": 50,"countryCode": "GB","currencyCode": "GBP","maxResults": 200}
Input Reference
What to Scrape
| Parameter | Type | Default | Description |
|---|---|---|---|
searchQueries | string[] | ["Tignanello 2019"] | Wine names or keywords to search on Vivino (e.g. "Barolo", "Penfolds Grange"). Include the vintage year or leave it out. Each query runs independently. |
startUrls | string[] | [] | Paste Vivino wine URLs directly. Each URL is fetched as a single wine. |
Results
| Parameter | Type | Default | Description |
|---|---|---|---|
maxResults | integer | 100 | Maximum number of wines to return across all queries and URLs. Set to 0 for unlimited. Start with 10β50 to test, then increase. This caps wines only β when reviews are on, each wine adds up to maxReviewsPerWine review rows on top of this number. |
vintageHandling | select | Smart (detect year automatically) | How vintage years are matched: detect a year in your query automatically, match the exact year you typed, or ignore the year and return every vintage of the wine. |
Detail
| Parameter | Type | Default | Description |
|---|---|---|---|
includeTasteProfile | boolean | true | Collect the taste profile β body, acidity, tannins, sweetness, fizziness, dominant flavor notes, and food pairings. |
Reviews
| Parameter | Type | Default | Description |
|---|---|---|---|
includeReviews | boolean | false | Also collect user reviews. Each review is its own result row, added on top of the maxResults wine count, so total results grow with the number of reviews collected. |
maxReviewsPerWine | integer | 10 | Maximum reviews to collect per wine (across all of its vintages) when reviews are on. Up to 100. Ignored when reviews are off. |
Localization
| Parameter | Type | Default | Description |
|---|---|---|---|
countryCode | select | United States | Country market used for pricing and availability. 23 countries supported. |
currencyCode | select | US Dollar | Currency for wine prices (ISO 4217). 15 currencies supported. |
Output
Every row carries a recordType field β wine or review β so you can filter cleanly downstream.
Wine (recordType: "wine")
{"recordType": "wine","wineId": "1652","vintageId": "159365358","name": "Tignanello","url": "https://www.vivino.com/en/tignanello/w/1652","winery": "Antinori","vintage": "2019","wineType": "Red","region": "Toscana","country": "Italy","grapes": ["Sangiovese", "Cabernet Sauvignon", "Cabernet Franc"],"averageRating": 4.6,"ratingsCount": 8567,"ratingIsWineLevel": false,"price": 159.99,"currency": "USD","imageUrl": "https://images.vivino.com/thumbs/example.png","foodPairings": ["Beef", "Lamb", "Game (deer, venison)"],"description": "A Tuscan icon blending Sangiovese with Bordeaux varieties.","alcoholContent": 13.5,"body": 4.2,"acidity": 3.1,"tannins": 3.8,"sweetness": 1.4,"fizziness": null,"flavorNotes": [{ "group": "oak", "score": 34699, "count": 240 },{ "group": "red_fruit", "score": 29551, "count": 209 }],"inputSource": "search","searchQuery": "Tignanello 2019","scrapedAt": "2026-08-25T14:30:00Z"}
Core Fields
| Field | Type | Description |
|---|---|---|
recordType | string | Always "wine" |
wineId | string | Vivino wine identifier |
vintageId | string | Vivino vintage identifier β the rated, priced bottle |
name | string | Wine name |
url | string | Canonical Vivino wine URL. Paste it straight back into startUrls for a full re-fetch |
winery | string | Winery / producer name |
vintage | string | Vintage year, or the literal "N.V." for non-vintage wines. Always filled |
wineType | string | Red, White, RosΓ©, Sparkling, Dessert, or Fortified |
region | string | Wine region |
country | string | Country of origin |
grapes | string[] | Grape varieties in the blend |
imageUrl | string | Bottle / label image |
description | string | Wine description and tasting note, when Vivino has one β roughly half of wines carry one |
alcoholContent | number | Alcohol by volume (ABV %), filled on about nine wines in ten |
inputSource | string | search or url β how this row was found |
searchQuery | string | The query or URL that produced this row |
scrapedAt | string | ISO timestamp of extraction |
Ratings & Pricing
| Field | Type | Description |
|---|---|---|
averageRating | number | Community average rating, 1β5. Empty when Vivino has too few ratings on the bottle to publish a score β never 0, because 0 is not a rating anyone gave |
ratingsCount | integer | Number of community ratings behind the average. Always filled, including when averageRating is empty β that is the "rated 20 times, no score published yet" case |
ratingIsWineLevel | boolean | false when the score belongs to this exact vintage. true when it does not β either the wine's overall score is standing in, or Vivino has published no score at either level yet, in which case averageRating is empty while ratingsCount still shows how many people rated the bottle |
price | number | Price in the selected currency, when Vivino lists a merchant offer. Back-vintages and rare bottles frequently have none |
currency | string | Currency code (ISO 4217) |
foodPairings | string[] | Vivino's suggested food pairings |
Taste Profile
Populated when includeTasteProfile is on. Vivino measures different axes for different wine types β tannins on reds, fizziness on sparkling β so a still wine returns no fizziness score and a sparkling wine returns no tannin score.
| Field | Type | Description |
|---|---|---|
body | number | Light-to-full body score |
acidity | number | Soft-to-acidic score |
tannins | number | Smooth-to-tannic score (red wines) |
sweetness | number | Dry-to-sweet score |
fizziness | number | Still-to-fizzy score (sparkling wines) |
flavorNotes | object[] | Dominant flavor-note groups, each with a group name, a score (how strongly the community tasted it), and a count (mentions behind it) |
Review (recordType: "review")
Emitted only when includeReviews: true. Capped at maxReviewsPerWine per wine.
{"recordType": "review","wineId": "1652","vintageId": "159365358","wineUrl": "https://www.vivino.com/en/tignanello/w/1652","username": "winelover_42","rating": 4.5,"comment": "Silky tannins, dark cherry, and a long finish. Worth the splurge.","date": "2026-03-18T09:12:00Z"}
| Field | Type | Description |
|---|---|---|
recordType | string | Always "review" |
wineId | string | Parent wine identifier |
vintageId | string | Parent vintage identifier |
wineUrl | string | Parent wine URL |
username | string | Reviewer's Vivino username |
rating | number | Reviewer's own rating (0β5) |
comment | string | Full review text |
date | string | Review date |
Tips for Best Results
- Strip the vintage to track a wine across release years. Set
vintageHandlingto "Ignore vintage" and you get every year of a wine β ideal for charting how a label's price moves from current release to back vintage. Release years the producer never actually bottled are removed for you, so the price curve you plot is built from bottles that exist. - "Match exact vintage" returns fewer wines by design. Pinning a query to one year narrows the pool hard: "Sassicaia 2019" returns 44 wines on that year versus 396 across all years. If you set
maxResultsto 100 and get 44, that's the full set for that vintage, and the run tells you so when it finishes. Use "Ignore vintage" when you want volume rather than precision. - Weight ratings by their count, and treat an empty rating as "no score yet". A 4.6 from 50,000 tasters is a far stronger signal than a 4.6 from 8, so sort on
ratingsCountalongsideaverageRating. Vivino withholds an average entirely until a bottle clears its threshold, so newer and rarer releases arrive withaverageRatingempty andratingsCountstill filled β filter onaverageRatingbeing present before you rank, or you will bury bottles that simply have not been scored. - Filter on
ratingIsWineLevelwhen the vintage year matters. About two rows in five (39.7%, measured over 1,527 rows) carrytrue, meaning the score is not that exact vintage's own β far more than a spot check suggests, and it runs from 15% on a Champagne search to 64% on a single-winery catalog sweep. Roughly a third of those flagged rows have no published score at all rather than a substituted one. KeepratingIsWineLevel: falsefor a strict vintage-by-vintage comparison; if you keep the flagged rows too, checkaverageRatingis present before you rank on it. - Expect thinner detail on rare back-vintages. Tasting notes, food pairings, taste scores, and prices all come from Vivino's community and merchant network, so a flagship current release is richly described while an obscure single-barrel bottling from decades ago may carry only name, winery, region, and vintage. Food pairings land on 96.5% of wines across broad varietal searches but nearer three in four on a deep single-winery sweep. Plan for it rather than treating an empty field as an error.
- Reviews add on top of your
maxResultscap.maxResultslimits the number of wines; it does not bound reviews. Each review is a separate billable row added on top, capped atmaxReviewsPerWineper wine (across its vintages). So a 50-wine run withmaxReviewsPerWine: 100can return up to 50 wines + 5,000 reviews. Reviews are off by default β turn them on deliberately and setmaxReviewsPerWineto keep result counts predictable. - Set currency and country to your real market.
currencyCodecontrols the price currency andcountryCodelocalizes availability β match both to the market you sell into so the prices you see are the prices your customers see. - Mix names and URLs in one run, and start small. Combine a list of search terms with a list of specific Vivino URLs to cover broad discovery and exact lookups in a single pass. Run 10β50 results first to confirm the wines and fields match what you expect, then raise
maxResults(or set it to0for unlimited).
Pricing
From $1.80 per 1,000 results β and it gets cheaper as your Apify discount tier goes up.
| Results | No discount | Bronze | Silver | Gold |
|---|---|---|---|---|
| 100 | $0.21 | $0.20 | $0.19 | $0.18 |
| 1,000 | $2.15 | $2.05 | $1.90 | $1.80 |
| 10,000 | $21.50 | $20.50 | $19.00 | $18.00 |
| 100,000 | $215.00 | $205.00 | $190.00 | $180.00 |
Tiered pricing takes effect on 9 September 2026. Until that date every result is billed at a flat $1.80 per 1,000, the rate shown in the Gold column.
A "result" is any row in the output dataset β a wine or a single review. No compute charges β you only pay per result returned. Reviews are off by default; turning them on adds one billable row per review collected.
Integrations
Export data in JSON, CSV, Excel, XML, or RSS. Connect to 1,500+ apps via:
- Zapier / Make / n8n β Workflow automation
- Google Sheets β Direct spreadsheet export
- Slack / Email β Notifications on new results
- Webhooks β Trigger custom APIs on run completion
- Apify API β Full programmatic access
Legal & Ethical Use
This actor is designed for legitimate wine retail research, market analysis, catalog enrichment, and product discovery. Users are responsible for complying with applicable laws and Vivino's terms of service, including making reasonable-rate requests and respecting content usage rules. Review text and usernames are user-generated content β handle any personal data responsibly and in line with applicable privacy regulations. Do not use extracted data for spam, harassment, or any illegal purpose.