Sign up to access "Getting Started with Nuxt 3" right now.

going to look at data fetching, e.g. making a request to an external API, getting back the results, and doing something with them, which is probably what you're going

to be doing in your apps anyway. Now for this, we're going to go ahead and use JSON placeholder, which is just going to provide us a fake API for testing. And we're going to go ahead and grab a list of to-dos.

So let's head down to the section just here. And you can see that we've got a URL for to-dos. We can also access individual to-dos as well. So we can pretty much put together

an app that looks like we are listing some to-dos, clicking through, and seeing a particular to-do. So I'm going to go ahead and grab this URL here. And on this page here, where we're

faking going through to a particular to-do ID, we're actually going to now make an API request. So let's go ahead and define our script section. Again, we're going to have this as a script setup type.

And let's make a request. Now there's a couple of different variations of this. We can either use useAsyncData, or we can use useFetch. We'll take a look at the difference between them

in a moment. So the first thing we're going to do is use useAsyncData. Now with this, what we want to do is a weight on this. And here we're using a top level weight

inside of script setup. Now by making a request to this, this will actually use suspense, which is a view three feature. So it will block the page loading

until this has been made. And over the next couple of parts, we're going to look at some of the options that we can pass through to useAsyncData just

to make the experience a little bit better, depending on how you're requesting the data and what you need to do with it. OK, so how do we use useAsyncData?

Well, this is a function. And the first argument for this is going to be a key so Nuxt can differentiate between the request that we're making.

So we're going to just call this to do's. You could call this literally anything you like. But to do's kind of makes sense because it's going to be an index of to do's.

Now the second argument to this is going to be a closure. And we're going to use fetch and then pass this URL into here that we just grabbed from JSON placeholder. So we're making a fetch request inside of this closure here.

And the key for this is to do's. It's pretty much as simple as it gets for now. If we head over and give this a refresh, notice that nothing is really happening.

But in the background, we are making a request to JSON placeholder to grab that data back. Question is, how do we extract this from here? Well, we can just easily destructure this.

You could go ahead and assign this to a variable, which you could use inside of your template. Let's see what happens when we do that. So let's go ahead and output data and just

see what we get on the page. So you can see here that we do actually have an object back here with a data key. And that contains all of that information that we need.

And behind the scenes, like I said, this is using suspense within view three. So let's go ahead and destructure this so we can use it properly and neatly.

So we're going to go ahead and alias data to to do's. And that means that we can just dump the to do's on the page, which is effectively what's contained within that data.

If we give this a refresh, there we go. We now have an array of all of them to do objects. So that is as simple as it is to make a request synchronously within NUX 3.

So we're going to go ahead and iterate over all of them to do's and output a NUX link for each one. So let's create our div out in here and let's use V4 like we normally would in view.

And let's say to do in to do's. And let's go ahead and key this really importantly by the to do ID, which does exist within here. So let's say to do and ID.

And let's grab this link that we commented out and pop that just inside of here. So let's go and give this a refresh. And there we go.

We now have a list of all of our to do's from that URL. Really, really simple to make a request to an API and get the results back. Now, of course, in here, what we want to do

is output the relevant information. So we can just do that as we normally would. To do and name or title. Let's go over.

There we go. And of course, now what we can do is we can link up the ID within that page that we created earlier.

So we can just pass the to do ID directly into there. So let's go ahead and click on the first one. And that goes through to do's one, two, three, and so on and so forth.

So we've now made a request and we can now link through. Great. So we're going to dive into some of the options we can pass through to use async data later.

But there's a slight variation to this if you didn't necessarily want to explicitly set a key and you don't mind Nuxt doing that for you. So let's go ahead and just comment this out

and look at another variation of making a request, which is actually much shorter. So this is using useFetch, like I mentioned earlier. It works in exactly the same way,

but all we need to do is pass through the URL. Nuxt will automatically generate a key for you and you'll just get the data back in the same way. So let's just do this in order.

We want to go ahead and grab data, call it to do's, and we're doing that by awaiting on useFetch. And we're just going to pass the URL that we want to make a request to,

which is this one just here. So we don't need to define out this callback. We don't need to useFetch explicitly. We just pass the URL in.

So if you just wanted to make a request through to a URL, you didn't really care about naming this. You would use useFetch. Let's go over, give that a refresh,

and you can see this works in exactly the same way. Okay, let's head over to the next couple of parts and see some of the options that we can pass through when we are making requests like this.