Let's get started now to get started.

A p I stands for application programming interface, which is just a fancy way of saying what one application exposes to another.

That is the A P I.

Let's take an example of a restaurant to describe how in a P I works in non technical terms.

So when you go to a restaurant, you don't go directly up to the chef and tell him what you want to order.

You need to look at the menu and order something off of the menu because the menu tells you what the restaurant offers that.

Is there a P I this menu the ape.

I essentially tells you what that certain application is giving to you and the things that you can use from the application.

So you go to the restaurant and you order something off of that menu.

Then, after you order something from that menu, you tell them what you want.

That restaurant is going to give you whatever you ordered off of that menu.

They're gonna give you back data.

So when you access an A P I that a p I, you're going to send it what you want, and then it will send you back information based on what you want it.

But if you go to this restaurant, for example, a steak restaurant and you try to order a peanut butter jelly sandwich, they're going to throw on air at you.

They're going to tell you we don't serve peanut butter jelly sandwiches.

You have to choose something on the menu, and this makes a P.

I sick here because they only expose what you want to expose to the rest of the world.

For example, a Web application is not going to expose to you the database with all the user's information of passwords.

They're only going to expose to you the log in and sign up pages and not the actual database itself.

This makes that website secure because they're only exposing the parts that they want to.

Some of the most common forms of AP eyes that you'll run into as a developer are going to be rest AP eyes on the Web and library AP eyes from code that you pull into your project was first talk about these web AP eyes which are going to be most likely rest ap eyes thes ap eyes exposed.

Different endpoints, also known as you girls, which you can access to get certain data from that a p I You can also access these end points in order to modify data on these servers.

But it only is what the application actually exposes to you and wants to let you modify.

For example, you may be able to update a user through arrest FBI, but they're not going to let you update the password.

They're only gonna let you update the name in the E mail.

For example.

You also appealed to get users from the A p I, but they're not going to return to you.

The password of the user will just give you the name and the email.

This is a way that these servers can be secured by only exposing the information they want through this AP I, which is the contract that the server and the client are having between each other.

The other most common AP I, which is not really referred to commonly as an a p I but is still technically a P.

I is an actual library that you pull into your code.

Thes libraries have a bunch of different methods to find on them that do specific things when you call them and return to your specific data when you call them.

This is exactly what in a P I is.

It's a contract between this library code that you've installed and your actual project, that using that libraries code, you have different ways that you can access it on lee the methods that they exposed and you aren't able to access the internals of that library unless it's through the methods that the A p I of the library exposes to you.

The common theme with AP Eyes is that they only exposed to you exactly what they want you to be with the access and hide away absolutely everything else that they can in order to make their A PR as secure as possible.

Also commonly, with Web apres, you're going to need some form of token to authenticate yourself with this AP I, which will allow the application to know whose access in the A P I in order to limit what that person can access based on their specific permissions.

In conclusion, AP Eyes are absolutely everywhere, from technology to non technology related fields, and it's really just a contract between two things with how they can interact with one another.

It's mostly used to make things more secure and easier to use because you know how you can use something and it hides away all the stuff that you cannot access, which makes it sick here.

And that's all in a P.

I is.

Have you guys enjoyed this video?

Please mention to check on my other videos where you're going to be linked.

Over here, I subscribe to the channel for more videos just like this.

Thank you guys very much for watching and have a good day.