datawebotLiv-ex wine data: LWIN identifiers, price measures and APIs
Explore Liv-ex LWIN identifiers, fine-wine price measures and documented APIs. Separate public LWIN reference data from licensed market data and website access.
Liv-ex serves wine professionals through an exchange and data services
Liv-ex describes its Exchange as a business-to-business service for wine professionals, combining market information with the ability to price, buy and sell. Its current homepage says Liv-ex does not hold stock or trade. Keep the exchange, public LWIN reference resource, licensed market data and logistics as distinct service surfaces; none is a consumer retail catalog.
Scroll to compare →
| Liv-ex surface | Question it serves | Keep distinct |
|---|---|---|
| Wine Exchange | Member trading, bids, offers and settlement activity. | A member transaction is not a consumer-store offer. |
| Market data and insight | Price measures, market analysis, time series and indices. | A public product description does not make its data openly accessible. |
| LWIN | Common product identity for wine and spirits across systems. | An identifier is not a price, stock state or transaction. |
| Logistics | Movement and operational services for the wine trade. | Logistics endpoints are not market-data fields. |
LWIN length identifies the record grain
Liv-ex describes LWIN as an identifier for wine and spirits. The first seven digits identify the product; longer forms append vintage, bottle size and pack size. Store the code as an identifier string and retain its length so a product-level match is not mistaken for a vintage, bottle or case-level match.
Scroll to compare →
| LWIN form | Fields represented | Matching use |
|---|---|---|
| LWIN7 | Product identity. | Group the wine or spirit independently of vintage and package. |
| LWIN11 | Product plus vintage. | Match a specific vintage; bottle and pack are not represented. |
| LWIN16 | Product, vintage and bottle size. | Separate, for example, 75cl and magnum bottlings. |
| LWIN18 | Product, vintage, pack size and bottle size. | Keep a case such as 12 bottles of 75cl separate from a single bottle. |
Liv-ex price measures describe different evidence
The current Liv-ex price definitions use different inputs, populations and time windows. Preserve the exact measure name with its observation time or averaging period. Market Price is based on advertised stock, Last Trade is a completed Liv-ex exchange trade, and Offex summarizes member-reported activity outside the Exchange.
Scroll to compare →
| Measure | Current source definition | Comparison check |
|---|---|---|
| Market Price | Likely price for SIB-compliant stock, based on the lowest prices advertised by leading stockholders in the EU. | An advertised-market reference, not a completed transaction. |
| Mid-Price | Midpoint between the highest live bid and lowest live offer, validated against additional data including transactions. | Keep separate from a trade price; the method uses more than the midpoint alone. |
| Average List Price | 30-day mean price for stock listed by Liv-ex merchants. | A listing average, not the amount every buyer paid. |
| Last Trade | The most recent Liv-ex trade for the wine. | Retain the trade timestamp and bottle/pack identity where available. |
| Bid and Offer | Prices at which Liv-ex trading members are currently bidding to buy or offering to sell. | Capture both side and observation time; these are live order states. |
| Auction Price | 30-day average collected from major auction houses. | Keep auction observations separate from exchange trades and current offers. |
| Offex | Anonymised 30-day average from member-reported transactions through their own sales channels outside the Exchange. | The source is member-submitted off-exchange activity, not a Liv-ex Exchange trade. |
Choose a Liv-ex API family by the data task
The current API Library groups data and analysis services separately from trading and logistics operations. These examples describe the published catalogue only. Membership, product subscription, tier limits, credentials and reuse rights determine which service a business may use.
Scroll to compare →
| API family | Published purpose | Workflow fit |
|---|---|---|
| Wine Data API | Attributed wine information, such as drinking windows, for an LWIN11 or list. | Enrich an identified wine record while preserving attribution. |
| Market Price and Benchmark API | Bulk Market Price, Last Trade or Benchmark data for LWIN11, LWIN16, LWIN18 or a list. | Compare price measures at the intended identifier grain. |
| Price Data and Time Series Export APIs | Live and historical market, trade, auction or release prices; historical series for an LWIN or index. | Build licensed valuation or price-history workflows with date and measure fields. |
| Auction Events, Offex and List Comparison | Historical auction data, member-supplied off-exchange data, and offers by selected businesses. | Keep each market evidence type and its source population separate. |
| Critic Data APIs | Scores, tasting notes and drinking dates from wine publications to which the customer subscribes. | Respect publication-specific subscription and licensing scope. |
| Trading, positions and logistics APIs | Exchange orders and positions, account operations, cellar stock and movement. | Treat as member operations, not general catalog or open market-data endpoints. |
Website access and licensed data have separate terms
Liv-ex’s Website Terms exclude membership, information and data services, trading, and logistics from that website agreement. The Website Terms restrict large-scale collection from the Site, including AI or machine-learning use, and restrict copying and linking. The Membership Terms separately describe API access, member licences, tier-based limits, an AI licence route and member obligations. These are different scopes; a listed API is not proof of unrestricted access.
Scroll to compare →
| Published boundary | What Liv-ex states | How to read it |
|---|---|---|
| Website Terms §1.2 | Membership, information/research/data services, trading and logistics have separate terms. | Do not apply the public-site terms as the complete description of licensed services. |
| Website Terms §§11.3–11.5 | Large-scale data collection and AI/ML training are restricted; copying, redistribution, linking or framing also have stated limits. | Treat public-site content separately from a documented member data product. |
| Membership Terms §§9.9–9.10 | AI use has a licence route; data may be delivered through a Liv-ex API. | API availability does not grant every use or redistribution right. |
| Membership Terms §§9.14–9.17 | Large-scale collection is restricted and data quantities/types can be limited by agreement or membership tier. | Check the specific product, account and contract terms. |
| Membership Terms §§37.6 and 37.8 | Members have stated restrictions on brand terms in digital advertising and automated gathering of Site content. | Keep these statements within their member-terms context; this guide is not legal advice. |
A useful wine-data record preserves identity, measure and rights
A robust internal model keeps a wine or spirit identity separate from its market evidence. The fields below are a proposed analysis schema, not a Liv-ex response or a current market record. Liv-ex describes LWIN as free to download under a Creative Commons licence; that reference resource should not be conflated with licensed price, transaction or member data.
Scroll to compare →
| Record layer | Useful fields | Why retain it |
|---|---|---|
| Identity | LWIN string, code length, product name, producer, region, colour and classification when available. | The LWIN length indicates which identity attributes are encoded. |
| Vintage and package | Vintage, bottle size, pack size and unit count. | Compare the same bottle and case basis instead of mixing package levels. |
| Market observation | Named measure, value, currency, unit, source class and observation timestamp or averaging window. | A 30-day average, live offer and completed trade answer different questions. |
| Data provenance | Named API or data product, retrieval time, source attribution and any transformation. | A result should remain traceable to the licensed service and method. |
| Rights context | Account or product scope, permitted internal or republished use, AI licence status and display conditions. | Entitlement and redistribution are separate from record structure. |
Content reviewed 2026-10-02.