All language subtitles for 7. REST APIs

af Afrikaans
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
ca Catalan
ceb Cebuano
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean Download
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese Download
pa Punjabi
ro Romanian
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen Download
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:01,360 --> 00:00:04,300 In our next section we will talk about the rest. 2 00:00:04,330 --> 00:00:05,560 AP ice 3 00:00:08,540 --> 00:00:19,040 let's start with the API and firstly I want to talk about what an API is and why it is important API 4 00:00:19,040 --> 00:00:22,510 stands for application programming interface. 5 00:00:22,520 --> 00:00:30,210 And basically it is something that allows one piece of software to talk to another. 6 00:00:30,230 --> 00:00:33,920 Now there is lots of different kind of API. 7 00:00:33,950 --> 00:00:42,650 But when you hear people talk about Twitter's API or Google's API what they are talking about is an 8 00:00:42,660 --> 00:00:49,150 arrest API which stands for representational state transfer. 9 00:00:49,160 --> 00:00:58,700 Now it doesn't have to be the case but usually arrest the API works pretty much the same way a website 10 00:00:58,790 --> 00:00:59,840 does. 11 00:01:00,050 --> 00:01:09,170 You make a call from a client to a server and you get data back over the issue to be protocol OK. 12 00:01:09,530 --> 00:01:17,690 Once you try to reach a web page for example simply what's going on is there is a P.C. in here and this 13 00:01:17,690 --> 00:01:28,760 P.C. is sending some issue to be requests to the web server and the web server is responding back with 14 00:01:28,760 --> 00:01:31,740 the extra tip your responses. 15 00:01:31,760 --> 00:01:33,840 OK. 16 00:01:34,090 --> 00:01:43,930 I think one of the best ways to show the many similarities between arrest API call and loading and normal 17 00:01:43,930 --> 00:01:47,090 web page can be found with Facebook. 18 00:01:47,150 --> 00:01:55,840 Graph API for example when you browse YouTube's Facebook page which is Facebook dot com slash YouTube 19 00:01:55,870 --> 00:02:01,510 and you know we are all familiar with what our Facebook page looks like. 20 00:02:01,510 --> 00:02:06,300 It shows how many legs that YouTube page has and things like that. 21 00:02:08,330 --> 00:02:14,550 Now lets browse the graph that Facebook that comes slice here too. 22 00:02:14,930 --> 00:02:19,980 And what we get back is a response to our API request. 23 00:02:20,000 --> 00:02:28,110 This time we have made an API request in our browser to Facebook Graph API. 24 00:02:28,130 --> 00:02:37,910 Now what we get back might appear to be gibberish to the human eye but it is actually javascript object 25 00:02:37,910 --> 00:02:41,540 notation or Jason for meta data. 26 00:02:41,720 --> 00:02:50,990 It is structured data organized according to key value pairs the same way an Excel spreadsheet is structured 27 00:02:50,990 --> 00:02:57,250 with the key value pairs and you might ask for the data that is in cell. 28 00:02:57,260 --> 00:03:06,020 You can ask a Jason array for the data if you want to know how many likes this Facebook page had for 29 00:03:06,020 --> 00:03:09,220 the data contained on the key legs OK. 30 00:03:09,260 --> 00:03:11,310 You can see it in here. 31 00:03:11,870 --> 00:03:19,730 Yeah there is the how many likes that YouTube Facebook page has right now. 32 00:03:19,790 --> 00:03:30,710 OK and a all modern programming languages some will be able to interpret these Jason responses so one 33 00:03:30,710 --> 00:03:38,080 more concept I want to introduce the idea of parameters and now let's Bro's. 34 00:03:38,180 --> 00:03:48,140 This web page graph Facebook dot com slash YouTube question Mark Fields equals to idea name and likes 35 00:03:48,770 --> 00:03:58,400 in this page you can see that only IDI name and likes have been returned. 36 00:03:58,400 --> 00:04:08,790 That is because these parameters have filtered the data that we get out of this response until now we 37 00:04:08,790 --> 00:04:12,730 have only been consuming data from API. 38 00:04:12,750 --> 00:04:16,320 But you can also write data to API. 39 00:04:16,680 --> 00:04:25,130 For this purpose it would be good to know H2 teepee request methods which most importance are a CTP 40 00:04:25,130 --> 00:04:37,260 post and a to b get a get request is what you use to consume to it and yet requests are used to read 41 00:04:37,260 --> 00:04:47,820 three resource representation and information only and not to modify it any way as yet requests do not 42 00:04:47,820 --> 00:04:50,330 change the state of the resource. 43 00:04:50,400 --> 00:05:00,000 These are safe to be safe methods opposed through requests for writing data to API in the best practice 44 00:05:00,030 --> 00:05:05,010 is to actually put the data in the body of the request. 45 00:05:07,660 --> 00:05:12,370 Now let's focus on the networking again. 46 00:05:12,370 --> 00:05:22,030 Let's have a look at how we are using rest api is on network automation Rest Api are not bound to API 47 00:05:22,030 --> 00:05:28,520 s and they are used to communicate between an application and and network controller. 48 00:05:29,430 --> 00:05:39,480 Specifically these APIs are using entity P for us to exchange information using Jason format typically 49 00:05:39,480 --> 00:05:44,820 and we will talk about from Jason format on the next slides. 50 00:05:45,390 --> 00:05:54,420 But there is an issue and that is there are several ETP verbs that we can use if we are creating an 51 00:05:54,480 --> 00:05:55,110 API. 52 00:05:55,110 --> 00:06:02,170 And if we want it to be easily supported we we should stick to some sort of standard. 53 00:06:02,280 --> 00:06:09,340 So somebody else is gonna be able to look our API is and be able to support it. 54 00:06:09,420 --> 00:06:19,500 So how can we have as standardized to approach to using these Asian dippy verbs in our API as guys for 55 00:06:19,500 --> 00:06:30,150 those purpose we are using a module named crop which is used by software industry for the four primary 56 00:06:30,150 --> 00:06:40,800 actions performed by an application and they are create reads Update and delight. 57 00:06:40,800 --> 00:06:49,560 For instance if using the note bounds Rest Api of a DNA controller you might want to create something 58 00:06:49,590 --> 00:06:55,670 new like and new security policy from a programming perspective. 59 00:06:55,680 --> 00:07:05,400 The security policy exists as a related set of configuration settings on the DNA controller internally 60 00:07:05,400 --> 00:07:16,140 represented by variables to do that arrest client application would use a create action using the DNA 61 00:07:16,140 --> 00:07:26,160 center RESTful API that created variables on the DNA controller via the DNA center REST API. 62 00:07:26,160 --> 00:07:35,340 The concept of creating new configuration at the controller is performed via the api using a create 63 00:07:35,430 --> 00:07:44,550 action per the corrupt generic acronym and such that if you want to read something from the controller 64 00:07:44,790 --> 00:07:53,760 we can use the get verb if you want to update an existing record on the controller you can use put verb 65 00:07:54,120 --> 00:07:56,430 and if you want to delay that error. 66 00:07:56,430 --> 00:07:59,370 You can use the delayed s to keep your. 7410

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.