liquor.com APIliquor.com ↗
Access liquor.com cocktail recipes, ingredients, ratings, user comments, and editorial articles. Search by keyword or browse by category with 5 endpoints.
curl -X GET 'https://api.parse.bot/scraper/8e72ae31-915d-4350-b89a-49e4878138ce/get_recipe?url_or_slug=recipes%2Fmargarita' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetch a single cocktail recipe by its URL slug or full URL. Returns title, ingredients, instructions, ratings, article_id (for use with get_recipe_comments), and more.
| Param | Type | Description |
|---|---|---|
| url_or_slugrequired | string | Recipe URL slug (e.g. 'recipes/margarita') or full URL (e.g. 'https://www.liquor.com/recipes/old-fashioned/') |
{
"type": "object",
"fields": {
"url": "string - full URL of the recipe",
"tags": "array of tag strings",
"title": "string - recipe name",
"yield": "array of yield values",
"author": "string - recipe author name",
"rating": "object with ratingValue and ratingCount",
"cook_time": "string - ISO duration",
"prep_time": "string - ISO duration (e.g. PT3M)",
"article_id": "string - numeric ID for use with get_recipe_comments",
"total_time": "string - ISO duration",
"description": "string - recipe description",
"ingredients": "array of ingredient strings",
"instructions": "array of instruction step strings",
"date_modified": "string - ISO datetime of last modification",
"date_published": "string - ISO datetime of publication"
},
"sample": {
"data": {
"url": "https://www.liquor.com/recipes/margarita",
"tags": [],
"title": "Margarita",
"yield": [
"1",
"1"
],
"author": "Liquor.com",
"rating": {
"ratingCount": "1320",
"ratingValue": "4.3"
},
"cook_time": "PT0M",
"prep_time": "PT3M",
"article_id": "4787239",
"total_time": "PT3M",
"description": "The classic Margarita combines tequila, lime and triple sec for ultimate refreshment.",
"ingredients": [
"2 ounces blanco tequila",
"1/2 ounce orange liqueur",
"1 ounce lime juice, freshly squeezed",
"1/2 ounce agave syrup",
"Garnish: lime wheel",
"Garnish: kosher salt (optional)"
],
"instructions": [
"Add tequila, orange liqueur, lime juice and agave syrup to a cocktail shaker filled with ice, and shake until well-chilled.",
"Strain into a rocks glass over fresh ice.",
"Garnish with a lime wheel and kosher salt rim (optional)."
],
"date_modified": "2023-04-20T15:13:37.651-04:00",
"date_published": "2016-11-01T15:10:40.000-04:00"
},
"status": "success"
}
}About the liquor.com API
The liquor.com API exposes 5 endpoints covering cocktail recipes, editorial articles, category browsing, full-text search, and user comments. Use get_recipe to retrieve a single cocktail's title, ingredient list, prep and cook times, structured rating data, and an article_id that links directly to the get_recipe_comments endpoint for Disqus-sourced reviews.
Recipe Data
The get_recipe endpoint accepts either a URL slug (e.g. recipes/margarita) or a full URL and returns the recipe's title, author, tags, yield, prep_time, cook_time, and total_time in ISO duration format. The rating object includes both a ratingValue and a ratingCount, giving a quantitative signal of a recipe's popularity. The article_id field in the response is the key for fetching community feedback via get_recipe_comments.
Search and Category Browsing
search_recipes takes a query string and returns a ranked list of matching results, each with a title, url, thumbnail, and category. This works for ingredient-based queries like whiskey sour as well as spirit categories like rum. list_recipes_by_category accepts a category slug or full URL and returns a similar set of result cards, making it straightforward to enumerate all recipes under a given taxonomy node such as cocktail-and-other-recipes-4779343.
Comments and Editorial Content
get_recipe_comments requires the article_id from a get_recipe call and returns a comments array where each entry includes username, name, text, created_at, upvotes, and downvotes. The get_article endpoint handles editorial and guide content — pass an articles/ slug or full URL to get the article's title, author, date_published, and a body string with paragraphs separated by double newlines.
- Build a cocktail recipe database indexed by ingredient using
search_recipeswith spirit-name queries - Aggregate user sentiment for specific drinks by pairing
get_reciperatings withget_recipe_commentsupvote/downvote counts - Enumerate all recipes in a category with
list_recipes_by_categoryto populate a drinks menu app - Extract publication dates and body text from mixology guides via
get_articlefor content research - Track recipe popularity trends over time using
ratingCountandratingValuefromget_recipe - Collect structured cocktail metadata (prep time, yield, tags) for a nutritional or drinks-planning tool
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does liquor.com have an official developer API?+
What does get_recipe_comments return, and how do I connect it to a recipe?+
comments array with per-comment fields: username, name, text, created_at, upvotes, and downvotes, plus a total count. To use it, first call get_recipe with a recipe slug — that response includes an article_id string (e.g. 4787239) which you then pass as the required input to get_recipe_comments.Does the API return a full ingredient list with quantities for each recipe?+
get_recipe endpoint returns ingredients as part of its response, but individual ingredient objects are not currently broken out into separate quantity, unit, and name sub-fields in the documented schema. The API covers title, tags, yield, times, rating, author, and article_id as discrete fields. You can fork this API on Parse and revise it to add structured ingredient parsing if your use case requires normalized quantity and unit data.Does list_recipes_by_category support pagination for large categories?+
total count and a results array but does not expose a page or offset parameter for stepping through large result sets. It covers the recipe cards surfaced for a given category slug. You can fork this API on Parse and revise it to add pagination support if you need to retrieve deeper result pages.