WEBVTT

00:00.960 --> 00:01.560
Welcome.

00:01.600 --> 00:05.120
In this lesson, I'm going to briefly introduce you to APIs.

00:05.560 --> 00:11.640
Break down what they are, how they work, and when they are essential for building automations and

00:11.680 --> 00:13.160
agents in N810.

00:13.680 --> 00:16.760
In the next lesson, I will dive deeper into APIs.

00:17.880 --> 00:21.800
So basically API stands for Application Programming Interface.

00:22.120 --> 00:23.920
But don't worry about the technical name.

00:23.920 --> 00:27.480
It's just a way for different apps and services to talk to each other.

00:28.280 --> 00:32.360
As you can see, this is the definition from AWS.

00:33.600 --> 00:34.880
So what is an API?

00:35.160 --> 00:41.760
APIs are mechanisms that enable two software components to communicate with each other using a set of

00:41.760 --> 00:43.480
definitions and protocols.

00:45.240 --> 00:47.000
What does API stand for?

00:47.880 --> 00:53.920
API stands for Application Programming Interface, as I said, and it acts as a contract of services

00:54.000 --> 01:00.240
service between two applications defining how they communicate using requests and responses.

01:00.240 --> 01:02.910
Policies and how do APIs work?

01:03.510 --> 01:08.510
API architecture is usually explained in terms of client and server.

01:09.070 --> 01:15.470
The application sending the request is called the client, and the application responding is called

01:15.470 --> 01:16.190
the server.

01:16.910 --> 01:22.430
So now let's break down this down into simple terms with some real world examples.

01:25.430 --> 01:30.310
So at the basic level an API works like a request and response system.

01:30.870 --> 01:36.910
So first a client sends a request and this is an app or automation asking for data.

01:37.870 --> 01:39.910
A server processes the request.

01:40.070 --> 01:43.670
So this is the system storing or computing the data.

01:44.430 --> 01:49.470
And finally the server sends back a response and the requested information is returned.

01:50.270 --> 01:54.390
So APIs are everywhere and you are already using them daily.

01:54.390 --> 02:02.180
When you check flights on travel websites, it calls airline APIs to fetch real time ticket prices.

02:02.980 --> 02:05.220
Or, for example, when you order food.

02:05.220 --> 02:08.420
The app requests restaurant menus via an API.

02:08.940 --> 02:14.260
Places the order and tracks delivery updates in N810.

02:14.300 --> 02:17.820
We use APIs all the time to automate tasks.

02:18.340 --> 02:25.820
To wrap up, APIs act as a bridges between apps, allowing them to exchange data.

02:26.620 --> 02:32.460
Every automation and AI agent uses APIs to fetch, send, and process data.

02:32.860 --> 02:38.820
And APIs unlock the power of automation in N810, and this topic is very important.

02:39.260 --> 02:46.060
It's crucial to build automation and agents on any platform using any tools.

02:46.900 --> 02:53.500
If you know how to use APIs effectively, you can connect to almost any software or app that provides

02:53.500 --> 02:54.500
API access.

02:55.020 --> 02:59.060
So now let's dive deeper into APIs and explore them in more detail.