# WSTA Wine and Spirit Trade Events API

> WSTA wine and spirit trade calendar: UK tastings, judging and webinars with dates and venues

- Vendor: `wstawineandspirittradeeventsap` · version 1.0 · category Food · tags wsta api, wine tasting events api, wine trade events api, spirits trade events api, uk wine events api, event calendar api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/wstawineandspirittradeeventsap
- This document: https://apiclay.com/docs/wstawineandspirittradeeventsap.md
- OpenAPI 3.1: https://apiclay.com/api/wstawineandspirittradeeventsap/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `wstawineandspirittradeeventsap`
- Updated: 2026-11-18

## About

## WSTA Wine and Spirit Trade Events API

The trade event calendar of the Wine and Spirit Trade Association (WSTA), the UK body for the wine and spirit industry (The Events Calendar plugin on WordPress): about 90 upcoming portfolio and trade tastings, competition judging sessions, webinars and other industry events, each with start and end time (local and UTC), title, description, organiser, venue, category, image and links; one event by id; the venues; and the event categories.

Data comes from **wsta.co.uk** (https://wsta.co.uk). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/events?per_page=20`, or narrow with `start_date`, `end_date`, `search` or `categories=tasting`, then `/event?id=`.

### Routes

#### GET `/events` - Events
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| per_page | query | number | no | Events per page (default 5, up to 50). |
| page | query | number | no | Page, from 1. |
| start_date | query | string | no | From this date, `YYYY-MM-DD` (default: today). |
| end_date | query | string | no | Up to this date, `YYYY-MM-DD`. |
| search | query | string | no | Text search in titles and descriptions. |
| categories | query | string | no | Category slug or id from `/categories`: `tasting`, `judging`, `webinar` or `events`. |

Returns: `events` array (`id`, `title`, `description` (HTML), `url`, `image`, `start_date`, `end_date`, `utc_start_date`, `timezone`, `cost`, `website`, `categories`, `venue`, `organizer` (name, phone, email)), plus `total` and `total_pages`. Upcoming events only, earliest first.

#### GET `/event` - Event
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| id | path | string | yes | Event `id` from `/events`. |

Returns: one event with the same fields plus `json_ld` (schema.org Event).

#### GET `/venues` - Venues
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| per_page | query | number | no | Venues per page. |
| page | query | number | no | Page, from 1. |

Returns: `venues` array (`id`, `venue` (name), `address`, `city`, `zip`, `url`) and `total` (over 1,100, past events included).

#### GET `/categories` - Categories
No parameters.

Returns: `categories` array: `id`, `name`, `slug`, `count`.

### Caveats

- Events are posted by their organisers (importers, producers, generic bodies); `cost` is often empty, so follow `url` or `website` for registration. Titles may contain HTML entities such as `&amp;`.
- `organizer` entries can carry the organiser's phone number and email as published on the event; handle them under UK GDPR or other applicable privacy law.
- Descriptions and images belong to the WSTA and the organisers.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by wsta.co.uk.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /events — Events
- Gateway: `GET https://api.apiclay.com/v1/api/wstawineandspirittradeeventsap/events`
- Public query params: `per_page` (number), `page` (number), `start_date` (string), `end_date` (string), `search` (string), `categories` (string)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /event — Event
- Gateway: `GET https://api.apiclay.com/v1/api/wstawineandspirittradeeventsap/event`
- Public query params: `id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /venues — Venues
- Gateway: `GET https://api.apiclay.com/v1/api/wstawineandspirittradeeventsap/venues`
- Public query params: `per_page` (number), `page` (number)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /categories — Categories
- Gateway: `GET https://api.apiclay.com/v1/api/wstawineandspirittradeeventsap/categories`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/wstawineandspirittradeeventsap/events" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
