Whiskybase APIwhiskybase.com ↗
Access the Whiskybase database via API: search whiskies, browse distilleries, check marketplace prices, fetch new releases, and retrieve the Top 1000 rankings.
What is the Whiskybase API?
The Whiskybase API exposes 7 endpoints covering the full Whiskybase bottle database — including full-text search, distillery catalogues, marketplace buy/sell listings, and the community Top 1000 ranking. The search_whiskies endpoint alone returns up to 10 fields per bottle (name, brand, age, strength, vintage year, bottle year, size, rating, and photo URL), paginated in sets of 25 across as many pages as the result set requires.
curl -X GET 'https://api.parse.bot/scraper/1fa3ba9e-3cd6-4ffe-b2d7-0da0f2ba5f66/search_whiskies?query=Ardbeg' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search over the Whiskybase bottle database. Returns matching whiskies with name, brand, strength, rating, and photo URL. Sorted by relevance. Results are auto-iterated across pages of 25.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (1-based) for paginated results. |
| queryrequired | string | Search keyword to match against whisky names and brands |
{
"type": "object",
"fields": {
"page": "integer current page number",
"items": "array of whisky objects with id, name, brand, display_name, age, strength, bottle_size, vintage_year, bottle_year, rating, url, photo",
"total": "integer total number of matching results",
"total_pages": "integer total number of pages"
},
"sample": {
"data": {
"page": 1,
"items": [
{
"id": 152827,
"age": 5,
"url": "https://www.whiskybase.com/whiskies/whisky/152827",
"name": "Wee Beastie",
"brand": "Ardbeg",
"photo": "https://static.whiskybase.com/storage/whiskies/1/5/2827/366361-normal.png",
"rating": "83.87",
"strength": "47.4 %vol",
"bottle_size": "700 ml",
"bottle_year": 2020,
"display_name": "<div class=\"whisky-naming\"><div class=\"whisky-name\">Ardbeg Wee Beastie</div></div>",
"vintage_year": null
}
],
"total": 1505,
"total_pages": 16
},
"status": "success"
}
}About the Whiskybase API
Search and Bottle Data
search_whiskies accepts a query string and an optional page parameter, returning matched bottles with fields including id, name, brand, display_name, age, strength, bottle_size, vintage_year, bottle_year, rating, and a direct url to the bottle's Whiskybase page. The response also carries total and total_pages so you can paginate through large result sets. For batch lookups, bulk_search_whiskies accepts a comma-separated queries string of up to 10 terms and returns one result block per term, each tagged with the original query, an ok boolean, and the same item array — useful for normalising a list of bottle names in a single call.
Distilleries and Their Catalogues
get_distilleries lists every distillery in the database. By default it returns id, name, country, and whiskies_count. Setting include_location to true adds region, latitude, and longitude, with results paginated at 25 per page. Once you have a distillery's numeric id, pass it to get_distillery_whiskies to retrieve every bottle attributed to that distillery — each entry includes age, strength, and community rating.
Marketplace and Releases
get_marketplace_listings returns active buy/sell listings with price, seller, rating, and a link to the listing. An optional query parameter narrows results to a specific whisky or brand. get_new_releases surfaces the latest bottlings, filterable by year, with fields covering age, strength, size, bottled, and rating.
Top 1000 Rankings
get_top_1000_whiskies returns the Whiskybase community ranking for bottles that have received at least 15 votes. Each entry carries rank, id, name, age, strength, and rating. The votes field is present in the response schema but returns null in the current page layout.
The Whiskybase API is a managed, monitored endpoint for whiskybase.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when whiskybase.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official whiskybase.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a whisky price tracker by polling
get_marketplace_listingsfor a specific brand and recording thepricefield over time. - Populate a personal cellar app by using
bulk_search_whiskiesto resolve a list of bottle names to Whiskybase IDs in a single request. - Generate distillery profile pages using
get_distillerieswithinclude_locationto map latitude/longitude alongside bottle counts. - Create a new-release alert system by calling
get_new_releaseswith a specificyearand comparing results to a stored snapshot. - Filter the Top 1000 list by
strengthoragefields to surface high-ABV or vintage bottles for recommendation features. - Cross-reference
get_distillery_whiskiesresults with marketplace listings to identify bottles that are available for sale. - Seed a whisky comparison tool with community
ratingdata pulled from search results across multiple brands.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Whiskybase have an official developer API?+
What does `get_distilleries` return when `include_location` is set to true versus the default mode?+
id, name, url, country, and whiskies_count for all distilleries in one call. With include_location: true the response adds region, latitude, and longitude per distillery, but results are paginated to 25 per page — so you'll need to step through pages using the page parameter to retrieve the full list.Why does `get_top_1000_whiskies` return `null` for the `votes` field?+
votes field is still present in the response for forward compatibility, but its value is always null with the current page structure. The rating, rank, age, and strength fields are unaffected.Does the API expose individual bottle tasting notes, user reviews, or community comments?+
Can I filter the Top 1000 list by country, distillery, or whisky style?+
get_top_1000_whiskies returns the full ranked list without server-side filtering options — the country and distillery fields are not part of the Top 1000 response. You can filter the returned array client-side by name or age, or use get_distillery_whiskies with a known distillery ID to get ratings for a specific producer. You can also fork this API on Parse and revise it to add filtered ranking endpoints.