WhiskyHunter API

Beginner's Pick Food & Drink / No Auth Required Beginner HTTPS
Free to Use Varies (check documentation)

Overview

WhiskyHunter aggregates statistical data from past online whisky auctions, letting you track price trends for specific bottles over time. No API key or account is required—just send a GET request and receive JSON data. It is ideal for whisky enthusiasts or developers building price comparison tools.

Beginner Tip

No API key needed—just call the endpoint directly. Use /api/whiskies_data/ to get a list of all tracked whiskies with their auction statistics.

Available Data

WhiskyHunter data via REST API

Example Response

JSON Response
{
  "status": "success",
  "data": {
    "result": "Data from WhiskyHunter",
    "description": "Past online whisky auctions statistical data",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

name Full name of the whisky bottle
slug URL-safe identifier used to fetch individual whisky stats
auction_count Total number of auctions recorded for this whisky
winning_bid_average Average winning bid price in GBP across all auctions
winning_bid_max Highest winning bid price ever recorded

Implementation Example

Request
// ⚠️ Note: This URL may be a documentation page. Check official docs for actual API endpoint.
const url = "https://whiskyhunter.net/api/";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Empty response or 404 The endpoint URL has a typo or trailing slash is missing
Ensure the URL ends with a slash: https://whiskyhunter.net/api/whiskies_data/
No data for a specific whisky The whisky slug is incorrect or not yet tracked
First fetch the full list from /api/whiskies_data/ to find the correct slug for the whisky you want
CORS error in browser The API does not send CORS headers for browser requests
Call the API from a backend server or use a serverless function as a proxy

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Food & Drink
Difficulty Beginner
Verified: 2026-04-04

Related Tags

Similar APIs

View All →