All language subtitles for 5. Functions of Single Data API

OK, guys, welcome to the course of Lavallade EPDP editorial, this is our partner, 14.

Inside this video, we are going to create an API which will display the information of single data.

So if I go back to Ed, in the last video, we had completed all about our API as well as a list employs

API.

Now, inside this video, viewed over work over a single detail API in which we will pass employee ID

by the help of that employee, it will fetch only specific employee information.

So what I will do as we know that we have loaded employee model inside last video.

So first of all, on the behalf of this employee ID, we need to check that this employee accessed or

not.

If we do exist, then we need to return the response once the details of that employee otherwise employee

not found.

So simply what I will do it.

If employee model will put their condition, we will check that the ID that we have passed is equal

to it.

Column of DBL and we will use the existing method.

If the employee accessed that, it will return true value.

Otherwise employee not accessed Edmans false value.

So what I will do return its response will use Dewson early and inside that Litsa status equals to zero

message.

It's the employee.

Let's make the first litterers capital, so employee not found and we will return the status quo.

Let's say for zero for now.

Inside this block, it means to employ excessed.

So what I will do for you to stay employed details solice employed detail equals to employ model we

will use will matter to check our condition.

This is the idea value and we will use the first method after that simply let's return response.

Jaeson putting in any Litsa that status equals Tufan

message lets the employee found.

And finally, we'll add one more parameter, that is data and anxieties, will this employed detail.

Now, if you save all these changes back to man, if I copy this, you all go here back to EPA, dot,

BSP.

So we're using single employments.

We're calling it single employee matter.

So we need to copy this route back to Postman instead of listing employees.

This time we have a single highway employee and the Matadi.

We need to use a get request type and we need to pass employee ID into the wall.

So back to Postman.

So here we have the post I equals to get request type.

And if we pass two, as you can see that inside is two, we have this employee.

So when we pass inside the single employee out to click on send button, as you can see that we are

getting all about second employee detail.

But when we make two to 20, it means that this employee ID does not exist into our list.

So in that case, if we press send button, as you can see, that employee not found and he'll look

at the status code for 04, we are getting also we can control our status code.

What we had written here so successfully, guys, this is the video is only to get a single employee

detail.

Now, in the next video, we will discuss over update API.

So far this decision.

Guys, thank you for watching and have a great day.