Summary  
This chapter explains how to handle API responses by interpreting HTTP status codes, inspecting response headers, and parsing JSON response bodies to retrieve and use data.  

General domain of usage  
Weather applications

When you use an API to request information, the response you receive includes several important parts. The first thing you will notice is the status code. This is a number that tells you whether your request was successful or if there was a problem. For example, a status code of `200` means everything went well, while a code like `404` means the resource you asked for could not be found. Understanding these codes helps you quickly see what happened with your request.

Along with the status code, the API sends back a response body. This is where the actual data you asked for is delivered. If you requested weather information, the response body might include the temperature, humidity, and a description of the current conditions, usually in a format like JSON. The response body is what you use in your application to display information or take further action.

Another key part of an API response is the headers. These are pieces of extra information sent along with the response. Headers might tell you what type of data is in the response body, how long the data can be cached, or details about the server that sent the response. While you might not always need to use the headers directly, they often provide useful context that helps your application handle the response correctly.

By understanding status codes, response bodies, and headers, you can confidently interpret API responses and make your applications more reliable and responsive to different situations.

### Receiving and Interpreting Data from an API

Suppose you use a weather app on your phone. When you check the weather, the app sends a request to a weather API. The API responds by sending back data, usually in a format like JSON.

Here is a simple example of what the API response might look like:

```
{
  "location": "New York",
  "temperature": 72,
  "condition": "Sunny"
}
```

Your application receives this data. It then reads the values for keys like `location`, `temperature`, and `condition`. The app uses this information to show you: "New York: 72°F and Sunny."

You do not see the raw data. The app interprets it and presents it in a way you can easily understand. This is how most applications use APIs to get and display information for you.

Which statement best describes a typical API response

A beginner-friendly course introducing the core concepts of APIs, their types, how they work, and their role in modern technology. This course uses simple language and practical scenarios to help you understand APIs from the ground up, with easy quizzes to reinforce your learning.

Get started with the basics of APIs, their purpose, and how they fit into the world of technology.

Learn about the different kinds of APIs and how they are used in various situations.

Dive deeper into how APIs exchange information and how people understand and use them.

API Responses: Getting Information Back

API Responses: Getting Information Back