Welcome to the world of mixology with the Cocktail Database API – your gateway to a vast array of cocktail recipes! This comprehensive API empowers users to explore and create the perfect drink by providing access to thousands of recipes searchable by both name and ingredients.
Whether you're a seasoned bartender, a home mixologist, or simply someone seeking to impress guests at your next gathering, the Cocktail API caters to all levels of expertise. Dive into a rich repository of classic concoctions and innovative libations, each recipe meticulously curated to ensure an exceptional drinking experience.
Effortlessly search for your favorite cocktail by name or assemble the ideal concoction based on available ingredients. The API's user-friendly design and robust search functionality make it a valuable tool for enthusiasts, cocktail bars, and beverage businesses alike.
Developers can seamlessly integrate the Cocktail Database API into websites, apps, or point-of-sale systems, enhancing user experiences with dynamic and up-to-date cocktail recipes. Elevate your mixology journey, whether you're crafting signature drinks for a venue or experimenting with flavors in the comfort of your home. Cheers to endless possibilities with the Cocktail Database API!
Pass the name of the cocktail you want and receive the ingredients and instructions to prepare them.
Cocktail Recipe Apps:
Bar and Restaurant Menus:
Home Bartending Platforms:
Event Planning and Catering:
Educational Platforms:
Besides API call limitations per month, there is no other limitation.
Returns up to 10 cocktail recipes matching the search parameters.
Get Data - Endpoint Features
Object | Description |
---|---|
name |
[Required] name of cocktail. This parameter supports partial matches (e.g. bloody will match bloody mary and bloody margarita) |
[{"ingredients": ["3 cl vodka citron", "2 cl triple sec", "1.5 cl lemon juice"], "instructions": "Pour all ingredients into cocktail shaker, shake well with ice, strain into chilled cocktail glass. Garnish with sugar rim around the glass.", "name": "lemon drop"}, {"ingredients": ["1+1/4 oz Jack Daniel's", "3/4 oz triple sec", "2 oz sour mix", "lemon-lime"], "instructions": "Shake first 3 ingredients with ice and strain into ice-filled glass. Top with the lemonade or lemon-lime. Add ice and stir. Garnish with lemon slices and cherries.[1]", "name": "lynchburg lemonade"}, {"ingredients": ["1 c Pineapple (crushed, drained)", "1 c Sugar", "1 q Water (hot, for sugar)", "1 c Tea (black, strong)", "6 Cloves", "20 Coriander seeds", "1/2 t Cinnamon", "1 pt Brandy", "1 pt Rum", "1 q Water (boiling)", "4 Lemon (peels of 2, juice all 4)", "1 q Milk (hot)"], "instructions": "Dissolve the sugar in the first measure of water. Pour everything except the lemon juice and the milk into a large nonreactive container. Cover and let steep for 6 hours. Add the lemon juice and milk, mix well, then strain through cheesecloth until clear.", "name": "charles dickens lemon milk punch"}, {"ingredients": ["4 oz Red wine", "1 oz Simple syrup", "1/2 oz Lemon juice", "1 sli Lemon (for garnish)", "2 Raspberry (a couple for garnish, optional)", "1 spg Mint (for garnish, optional)"], "instructions": "Combine liquid ingredients. Pour back and forth between two halves of a cocktail shaker. Strain into a goblet over ice and garnish.", "name": "claret lemonade"}]
curl --location --request GET 'https://zylalabs.com/api/3160/cocktail+database+api/3358/get+data?name=bloody mary' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Cocktail Database API furnishes an extensive collection of cocktail recipes, including details such as ingredients, proportions, preparation methods, and garnishes.
Absolutely. The API supports ingredient-based searches, allowing users to discover cocktails based on the ingredients they have available or prefer.
The Cocktail Database API is regularly updated to ensure it reflects the latest trends, additions, and modifications to the world of mixology.
Yes, rate limits are in place to manage API usage fairly. Refer to the API documentation for details on rate limits and how to handle rate-limiting scenarios in your application.
Certainly. Developers can leverage the API to build recommendation systems based on user preferences, helping users discover new cocktails that align with their taste.
The Cocktail Database API returns detailed cocktail recipes, including the cocktail name, a list of ingredients, preparation instructions, and optional garnishes. Each recipe is structured to provide a comprehensive guide for mixing drinks.
The key fields in the response data include "name" (cocktail name), "ingredients" (list of ingredients), and "instructions" (step-by-step preparation method). These fields provide essential information for recreating each cocktail.
The response data is organized as a JSON array, where each cocktail recipe is represented as an object containing the key fields. This structure allows for easy parsing and integration into applications.
The endpoint allows users to search for cocktails by specific parameters such as cocktail name or ingredient. Users can customize their requests to find recipes that match their preferences or available ingredients.
Users can utilize the returned data by displaying cocktail names and recipes in apps or websites, allowing users to easily access and follow the preparation instructions. This enhances user engagement and promotes mixology exploration.
The endpoint provides information on cocktail recipes, including ingredient lists, preparation methods, and optional garnishes. This comprehensive data supports a wide range of mixology applications and user needs.
Data accuracy is maintained through regular updates and curation of cocktail recipes. The API ensures that the information reflects current trends and reliable recipes, enhancing user trust in the data provided.
Typical use cases include developing cocktail recipe apps, enhancing bar menus, creating home bartending platforms, and educational resources for mixology. The API serves as a versatile tool for various cocktail-related applications.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
574ms
Service Level:
100%
Response Time:
676ms
Service Level:
94%
Response Time:
8,462ms
Service Level:
100%
Response Time:
708ms
Service Level:
100%
Response Time:
261ms
Service Level:
100%
Response Time:
1,201ms
Service Level:
100%
Response Time:
1,223ms
Service Level:
91%
Response Time:
167ms
Service Level:
100%
Response Time:
2,063ms
Service Level:
100%
Response Time:
167ms
Service Level:
100%
Response Time:
7,964ms
Service Level:
100%
Response Time:
1,085ms
Service Level:
100%
Response Time:
1,310ms
Service Level:
100%
Response Time:
1,093ms
Service Level:
100%
Response Time:
1,138ms
Service Level:
100%
Response Time:
1,093ms
Service Level:
100%
Response Time:
3,183ms
Service Level:
100%
Response Time:
2,242ms
Service Level:
100%
Response Time:
586ms
Service Level:
100%
Response Time:
1,302ms