Overview
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.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/cocktail?name=martini" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/cocktail?name=martini', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/cocktail?name=martini",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/cocktail?name=martini", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
nameRequired | string | The name of the cocktail for which you want to get the recipe (e.g., martini) |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"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 |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- 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
Other ways to use Cocktail Recipe
Set up Cocktail Recipe on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Food: