Whisky Hunter

Whisky Hunter is a market research and data platform that aggregates historical auction data from online whisky auction houses into a single database. Its REST API exposes aggregated auction statistics, auction house information, and per-distillery data, letting you ingest bottle listings, trading volumes, winning bids, and distillery details for analysis and reporting.

Power end-to-end data operations for your Whisky Hunter API with Nexla. Our bi-directional Whisky Hunter connector is purpose-built for Whisky Hunter, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Whisky Hunter or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Whisky Hunter workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The Whisky Hunter API is a public REST API served from https://whiskyhunter.net/api/ that returns JSON. All monetary values are reported in GBP, and the underlying data updates infrequently, so a daily (24-hour) or longer ingestion cadence is recommended.

The Whisky Hunter public endpoints do not require authentication. The Nexla connector authenticates each request with an API key, which is sent in the Authorization header as a bearer token. If you have been issued a Whisky Hunter API key, have it available before creating your Nexla credential. If the endpoints you use are open, you can supply any placeholder value; Nexla will still send the header with each request.

For the current list of endpoints and response formats, refer to the Whisky Hunter API reference.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key used to authenticate requests to the Whisky Hunter API.

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Whisky Hunter API key in the API Key field. Nexla sends this value in the Authorization header as a bearer token on every request to the Whisky Hunter API.

   Treat your API key as sensitive information. If it is ever exposed, generate a new key and update this credential.

   For details about available endpoints and response formats, see the Whisky Hunter API reference.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Whisky Hunter connector tile, then select the credential that will be used to connect to Whisky Hunter, and click Next; or, create a new Whisky Hunter credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Whisky Hunter endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Auctions Data

This endpoint template retrieves auctions data from Whisky Hunter. Use this template when you need aggregated auction statistics — such as trading volumes, winning bids, and lot counts — for analysis, reporting, or integration purposes.

This endpoint returns auctions data as JSON. For details about the response structure and available fields, see the Whisky Hunter API reference.

[Rest API] List Auctions Info

This endpoint template retrieves auctions info from Whisky Hunter. Use this template when you need information about the auction houses that Whisky Hunter aggregates, for analysis, reporting, or integration purposes.

This endpoint returns auctions info as JSON. For details about the response structure and available fields, see the Whisky Hunter API reference.

[Rest API] List Distilleries Info

This endpoint template retrieves distilleries info from Whisky Hunter. Use this template when you need distillery details and per-distillery statistics for analysis, reporting, or integration purposes.

This endpoint returns distilleries info as JSON. For details about the response structure and available fields, see the Whisky Hunter API reference.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Whisky Hunter data sources can also be manually configured to ingest data from any valid Whisky Hunter API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Whisky Hunter data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.