Building with Winevery.

Accounts and access

Use your own Winevery account and keep API keys confidential. You are responsible for calls made with your keys. Rotate or revoke a compromised key from the developer dashboard. API credentials authorize public catalogue features, not personal cellar, journal or Passport records.

The Sandbox is for evaluation and personal projects. Paid self-service plans allow commercial application use within their published limits. Enterprise requirements are governed by a separate written agreement.

Billing, credits and cancellation

Paid API subscriptions renew monthly at the amount and currency shown in Stripe checkout. API subscriptions are separate from Wine Passport membership. Taxes, if applicable, are shown at checkout. Creating an account or a Sandbox key does not start a paid subscription.

Successful catalogue, search and wine-profile calls cost 1 credit; similarity costs 3 credits; food pairing costs 5 credits. Non-2xx requests do not consume credits but may count toward request-rate limits. Paid credits reset with your monthly billing period. Sandbox credits reset on the first day of each month in UTC. Unused credits expire. Self-service requests stop at your quota and do not incur automatic overage charges.

Cancel renewal in your developer dashboard. Paid access continues until the end of the paid period, then returns to Sandbox. Payment failure or an expired subscription can pause paid access. Contact hello@winevery.com about billing, refunds, plan changes or an incorrect charge. Mandatory statutory rights remain unaffected.

Permitted application use

You may display returned metadata within the subscribed application and cache it to operate that application while your subscription is active. Identify Winevery as the data source with a link to winevery.com where practical. Your subscription does not transfer ownership of the catalogue, third-party material or underlying identifiers.

Self-service subscriptions do not include permission to sell or redistribute the raw catalogue, expose a competing data feed, bulk-download the dataset, share API credentials between unrelated customers, or use returned data to train or sell a general-purpose model or dataset. Bulk delivery, redistribution, sublicensing and training rights require a separate written agreement with Winevery covering the requested fields and rights.

When paid access ends, stop further commercial use under that subscription. Contact us about retained-data rights if your product requires continued use of cached records. Independently held rights in your own or openly licensed data are unaffected.

Coverage and reliability

Public catalogue copy describes access to up to 2 million wines. The available API count is returned by the catalogue endpoint and can change as records are added, corrected, merged or removed. Field coverage varies by wine. Missing values are unknown. A wine profile does not establish that every vintage or bottle format is covered.

Wine information and matching reasons may be incomplete or out of date. Similarity and food pairing express possible matches using recorded attributes. This API release does not provide live merchant prices, stock availability or guaranteed taste outcomes. Check important product details with the producer or merchant.

Self-service plans have no contractual uptime SLA or guaranteed support response time. Enterprise service commitments must be agreed in writing. We may make compatible improvements to version 1; contact support if you need a migration arrangement for a material interface change.

Responsible use and support

Do not bypass quotas, distribute keys publicly, interfere with other customers or use multiple accounts to evade plan limits. Winevery may suspend keys or access to investigate misuse or protect service availability. Use wine-related features only for people of legal drinking age where they live.

Contact hello@winevery.com. Include your account email and a request ID for technical issues, never your full API key. See the API privacy notice, website terms and developer documentation.