Country_Name

Full_Name

Currency

Language

Capital_City

Calliing_code

Region

Sub_Region

In this course, the learner will learn some very interesting and useful endpoints of the REST Countries API.

countroies.tar.gz

Countries_API

The REST Countries API provides a vast database of countries’ metadata, including region, language, currency, calling code, and capital city. You can take full advantage of this API by utilizing it to feed online platforms that require essential country-related information.

You will start with an introduction to the REST Countries API. You will learn to search a country by its partial and full name. Next, you will learn to list countries that use the same currency or speak the same language. You will then learn how to find the capital city and calling codes to make phone calls. You will also learn to filter the response to an API call to extract the most relevant information. Finally, you will cover the integration of the REST Countries API into a demo application.

By the end of this course, you will have sufficient skills to integrate the REST Countries API into your application.

Get Started with the REST Countries API in JavaScript

The REST Countries API allows us to specify the output fields of a request made to an API endpoint. This can be especially useful when working with large datasets because it allows us to narrow down the results and focus on the most relevant information. For instance, if we are querying the REST Countries API database and only need to see a few specific fields, we can specify which fields we want to include in the response of our request. This can help to streamline our work by reducing the amount of data we need to process, making it easier to find the information we need.

We can specify the required fields in the REST Countries API request by using the `fields` parameter. We can append this query parameter with the URLs of the endpoints discussed earlier to filter the response.

Here are some examples of how to specify the required fields. In these examples, we will specify the fields and check the effect on the response.
## Filter a single field
In this example, we’ll only specify a single field to be returned in the response.
We’ll use the URL of the **All** endpoint, which returns the information about all available countries. The URL for this endpoint is `https://restcountries.com/v3/all`. We’ll append `fields=name` as a query parameter with this URL to get only the `name` field in the response.

 Click the “Run” button to fetch the specified field.

The REST Countries API allows us to specify the output fields of a request made to an API endpoint. This can be especially useful when working with large datasets because it allows us to narrow down the results and focus on the most relevant information. For instance, if we are querying the REST Countries API database and only need to see a few specific fields, we can specify which fields we want to include in the response of our request. This can help to streamline our work by reducing the amount of data we need to process, making it easier to find the information we need.

We can specify the required fields in the REST Countries API request by using the `fields` parameter. We can append this query parameter with the URLs of the endpoints discussed earlier to filter the response.

Here are some examples of how to specify the required fields. In these examples, we will specify the fields and check the effect on the response.
# Filter a single field
In this example, we’ll only specify a single field to be returned in the response.
We’ll use the URL of the **All** endpoint, which returns the information about all available countries. The URL for this endpoint is `https://restcountries.com/v3/all`. We’ll append `fields=name` as a query parameter with this URL to get only the `name` field in the response.

 Click the “Run” button to fetch the specified field.

Learn how to filer responses of the REST Countries API

Introduction

Search Functionalities

Filter Response

Country API Integration with React

Conclusion

Filter Response