Cocktail is a simple tool for getting cocktail recipes. It returns the ingredients, instructions, and more of the cocktail.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Cocktail Recipe response payload
}
}
About the Cocktail Recipe API
Cocktail works by querying a large database of cocktail recipes to retrieve the ingredients, instructions, and other details of a cocktail. It returns the cocktail recipe in a structured format.
What people use it for
- Bartending
- Use the Cocktail API to get cocktail recipes for bartending. Use the data to mix drinks, create cocktails, and serve beverages
- Party Planning
- Create party planning products by using the Cocktail API to get cocktail recipes. Use the data to plan events, organize menus, and prepare drinks
- Recipe Lookup
- Look up cocktail recipes by using the Cocktail API. Use the data to find recipes, discover new drinks, and explore mixology
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Cocktail Recipe
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Cocktail Recipe API do?
How do I authenticate Cocktail Recipe API requests?
How much does the Cocktail Recipe API cost?
How fast is the Cocktail Recipe API?
What response formats does the Cocktail Recipe API support?
What HTTP method does the Cocktail Recipe API use?
Request parameters — GET /v1/cocktail
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
nameRequired | string | martini | The name of the cocktail for which you want to get the recipe (e.g., martini) |
curl "https://api.apiverve.com/v1/cocktail?name=martini" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/cocktail
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"count": 5,
"filteredOn": "name",
"cocktails": [
{
"name": "Espresso Martini",
"glass": "martini",
"category": "After Dinner Cocktail",
"ingredients": [
{
"unit": "cl",
"amount": 5,
"ingredient": "Vodka"
},
{
"unit": "cl",
"amount": 1,
"ingredient": "Coffee liqueur",
"label": "Kahlúa"
},
{
"special": "Sugar syrup (according to individual preference of sweetness)"
},
{
"special": "1 short strong Espresso"
}
],
"ingredientCount": 4,
"estimatedStrength": "medium",
"preparation": "Shake and strain into a chilled cocktail glass."
},
{
"name": "Lemon Drop Martini",
"glass": "martini",
"category": "All Day Cocktail",
"ingredients": [
{
"unit": "cl",
"amount": 2.5,
"ingredient": "Vodka",
"label": "Citron Vodka"
},
{
"unit": "cl",
"amount": 2,
"ingredient": "Triple Sec"
},
{
"unit": "cl",
"amount": 1.5,
"ingredient": "Lemon juice"
}
],
"garnish": "Lemon slice",
"preparation": "Shake and strain into a chilled cocktail glass rimmed with sugar."
},
{
"name": "French Martini",
"glass": "martini",
"category": "Before Dinner Cocktail",
"ingredients": [
{
"unit": "cl",
"amount": 4.5,
"ingredient": "Vodka"
},
{
"unit": "cl",
"amount": 1.5,
"ingredient": "Raspberry liqueur"
},
{
"unit": "cl",
"amount": 1.5,
"ingredient": "Pineapple juice"
}
],
"preparation": "Stir in mixing glass with ice cubes. Strain into chilled cocktail glass. Squeeze oil from lemon peel onto the drink."
},
{
"name": "Dirty Martini",
"glass": "martini",
"category": "Before Dinner Cocktail",
"ingredients": [
{
"unit": "cl",
"amount": 6,
"ingredient": "Vodka"
},
{
"unit": "cl",
"amount": 1,
"ingredient": "Vermouth",
"label": "Dry vermouth"
},
{
"unit": "cl",
"amount": 1,
"ingredient": "Olive juice"
}
],
"garnish": "Green olive",
"preparation": "Stir in mixing glass with ice cubes. Strain into chilled martini glass."
},
{
"name": "Dry Martini",
"glass": "martini",
"category": "Before Dinner Cocktail",
"ingredients": [
{
"unit": "cl",
"amount": 6,
"ingredient": "Gin"
},
{
"unit": "cl",
"amount": 1,
"ingredient": "Vermouth",
"label": "Dry vermouth"
}
],
"preparation": "Stir in mixing glass with ice cubes. Strain into chilled martini glass. Squeeze oil from lemon peel onto the drink, or garnish with olive."
}
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
count | number | 5 | Number of cocktails returned |
filteredOn | string | "name" | Which parameter the results were filtered by |
cocktails | array[5] | The matching cocktail recipes | |
name | string | "Espresso Martini" | Name of the cocktail |
glass | string | "martini" | Glass the cocktail is traditionally served in |
category | string | "After Dinner Cocktail" | Category the cocktail belongs to, such as after dinner or pre-dinner |
ingredients | array[4] | Ingredients with their measures | |
unit | string | "cl" | Unit the measure is given in, such as cl or dash |
amount | number | 5 | How much of the ingredient to use |
ingredient | string | "Vodka" | Name of the ingredient |
ingredientCount | number | 4 | Number of ingredients in the cocktail |
estimatedStrengthPremium | string | "medium" | Alcohol strength estimate: strong, medium, light, or mocktail |
preparation | string | "Shake and strain into a chilled cocktail glass." | How to make the cocktail |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Cocktail Recipe calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/cocktail
No SDK to install — this is a plain HTTPS call to /v1/cocktail with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/cocktail" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/cocktail
Install the Node.js SDK, then call the Cocktail Recipe API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/cocktailconst res = await fetch("https://api.apiverve.com/v1/cocktail", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/cocktail
Install the Python SDK, then call the Cocktail Recipe API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-cocktailimport requests
res = requests.get(
"https://api.apiverve.com/v1/cocktail",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/cocktail
Install the C# / .NET SDK, then call the Cocktail Recipe API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.CocktailRecipeusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/cocktail");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/cocktail
No SDK to install — this is a plain HTTPS call to /v1/cocktail with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/cocktail", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/cocktail
No SDK to install — this is a plain HTTPS call to /v1/cocktail with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/cocktail");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/cocktail
No SDK to install — this is a plain HTTPS call to /v1/cocktail with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/cocktail")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Cocktail Recipe form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Cocktail Recipe API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Cocktail Recipe API.
Food
- Cocktail Recipe
- Nutrition
- Recipe Generator
Related articles
All articles →
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
Business Day Math Is Harder Than You ThinkWeekends, holidays, and country-specific rules make working day calculations surprisingly tricky. Here's what to watch for.Read