Learn how to search food items and cocktail recipes using TheMealDB and TheCocktailDB APIs.

Become a Python-based API Integrator

TheMealDB and TheCocktailDB APIs are REST APIs used to search food item recipes. This module is a hands-on guide for using these APIs. The module begins with an introduction to TheMealDB and TheCocktailDB APIs. We'll learn about the request and response structures of these APIs. Furthermore, we'll also learn about the different endpoints and how to use them. Then, we'll look at a demo application that will use these APIs to search for recipes. Lastly, we'll look at some recommendations and resources that will allow us to explore these APIs further.

Fetching Recipes with TheMealDB and TheCocktailDB APIs

## Request structure
The request for TheCocktailDB API contains the endpoint the user wants to call. Each endpoint serves a different function. Here is a list of the base URLs which can be used:

align-center

>**Note:** The API key `1` after `www.thecocktaildb.com/api/json/v1/` in each of these addresses is the development API that we talked about in the previous lesson.

These base URIs are combined with the query parameters to get the data we want.
## Response structure
The response structure will differ depending on whether our search criteria matched any cocktail from the database or not.
### In case of an unsuccessful request
If our search criteria don’t match any drink in the database, the result will contain only one element, `drinks` or `ingredients`, depending on whether the search was related to drinks or ingredients. The value of the returned object will be `null`.
### In case of a successful request
For a successful request, we’ll get different data for different endpoints. We’ll discuss the results of successful requests for these endpoints in detail in the upcoming lessons.

# Request structure
The request for TheCocktailDB API contains the endpoint the user wants to call. Each endpoint serves a different function. Here is a list of the base URLs which can be used:

>**Note:** The API key `1` after `www.thecocktaildb.com/api/json/v1/` in each of these addresses is the development API that we talked about in the previous lesson.

These base URIs are combined with the query parameters to get the data we want.
# Response structure
The response structure will differ depending on whether our search criteria matched any cocktail from the database or not.
## In case of an unsuccessful request
If our search criteria don’t match any drink in the database, the result will contain only one element, `drinks` or `ingredients`, depending on whether the search was related to drinks or ingredients. The value of the returned object will be `null`.
## In case of a successful request
For a successful request, we’ll get different data for different endpoints. We’ll discuss the results of successful requests for these endpoints in detail in the upcoming lessons.

Learn about the request and response structure of TheCocktailDB API.

Function	Base URI
Search cocktails by ingredient, first letter, or name	`www.thecocktaildb.com/api/json/v1/1/search.php`
Lookup cocktails or ingredients by database IDs	`www.thecocktaildb.com/api/json/v1/1/lookup.php`
Get a random cocktail recipe	`www.thecocktaildb.com/api/json/v1/1/random.php`
Filter cocktails by ingredients, alcoholic filters, categories, or glass type	`www.thecocktaildb.com/api/json/v1/1/filter.php`
	`www.thecocktaildb.com/api/json/v1/1/filter.php`	`www.thecocktaildb.com/api/json/v1/1/filter.php?i=Vodka`
List the available categories, glasses, ingredients, or alcoholic filters	`www.thecocktaildb.com/api/json/v1/1/list.php`

Module Overview

TheCocktailDB API

TheMealDB API

APIs Integration in Django

Conclusion

Request and Response Structure

Request structure