Sr Technical Content Strategist and Team Lead

The JavaScript Fetch API is the built-in way to make HTTP requests in modern
browsers and in Node.js 18+.
It returns Promises, so you can chain .then() calls or use async/await
instead of older patterns like XMLHttpRequest or jQuery’s $.ajax().
In this tutorial, you will send GET and POST requests, handle HTTP errors correctly, cancel slow requests, and compare Fetch with Ajax and Axios.
fetch('https://jsonplaceholder.typicode.com/users')
.then((response) => {
if (!response.ok) throw new Error(response.status);
return response.json();
})
.then((data) => console.log(data))
.catch((error) => console.error(error));
Deploy your frontend applications from GitHub using DigitalOcean App Platform. Let DigitalOcean focus on scaling your app.
fetch(url, options). It returns a
promise that resolves to a Response object, not parsed JSON.response.json(), response.text(), or response.blob() to read the
body. Each body-reading method returns its own Promise.fetch() only rejects on network failure. A 404 or 500 response still
resolves. Check response.ok or response.status before you parse the body.method, headers, and body. Use
JSON.stringify() when you send JSON. See
How to Work with JSON in JavaScript.async/await keeps request code readable. Pair it with try/catch
and the same response.ok checks you use in promise chains.AbortController cancels in-flight requests and sets timeouts. Pass
signal in the options object.To complete this tutorial, you will need the following:
async/await. Read the
Promises section
of
Understanding the Event Loop, Callbacks, Promises, and Async/Await in JavaScript.The JavaScript Fetch API is a browser and Node.js interface for requesting
resources over HTTP. You pass a URL (or a Request object) to fetch(). The
function returns a Promise that resolves when headers arrive, even when the
server returns an error status.
| Concept | What it means |
|---|---|
fetch() |
Starts an HTTP request. Second arg sets method, headers, body. |
Response |
Metadata plus body readers like .json() and .text(). |
Request |
A reusable description of a call you can pass to fetch(). |
For the full specification, see MDN: Fetch API.
The simplest call passes only a URL:
fetch(url)
fetch() returns a Promise. Chain .then() to handle a successful response:
fetch(url)
.then(function() {
// handle the response
})
Add .catch() for network errors (offline client, DNS failure, CORS block in
some cases):
fetch(url)
.then(function() {
// handle the response
})
.catch(function() {
// handle the error
});
.catch() does not run when the server returns 404 or 500. You handle
those status codes inside .then() by checking response.ok. The
error handling section below shows
the pattern.
This step loads ten users from the JSONPlaceholder API and renders them in an HTML list.
Create authors.html with a heading and an empty list:
<h1>Authors</h1>
<ul id="authors"></ul>
Add a script tag. Select the list with
getElementById
and create a
DocumentFragment
to hold list items before you attach them to the page:
<h1>Authors</h1>
<ul id="authors"></ul>
<script>
const ul = document.getElementById('authors');
const list = document.createDocumentFragment();
const url = 'https://jsonplaceholder.typicode.com/users';
</script>
Call fetch() and check response.ok before you parse JSON:
<script>
const ul = document.getElementById('authors');
const list = document.createDocumentFragment();
const url = 'https://jsonplaceholder.typicode.com/users';
fetch(url)
.then((response) => {
if (!response.ok) {
throw new Error(`HTTP ${response.status}`);
}
return response.json();
})
</script>
The first .then() receives a Response. Calling response.json() returns
another Promise with the parsed data. Add a second .then() to build list items
with
map(),
createElement,
and
appendChild:
<script>
const ul = document.getElementById('authors');
const list = document.createDocumentFragment();
const url = 'https://jsonplaceholder.typicode.com/users';
fetch(url)
.then((response) => {
if (!response.ok) {
throw new Error(`HTTP ${response.status}`);
}
return response.json();
})
.then((authors) => {
authors.forEach((author) => {
const li = document.createElement('li');
const name = document.createElement('h2');
const email = document.createElement('span');
name.textContent = author.name;
email.textContent = author.email;
li.appendChild(name);
li.appendChild(email);
list.appendChild(li);
});
ul.appendChild(list);
})
.catch((error) => {
console.error('Fetch failed:', error);
});
</script>
This is the complete authors.html file:
<h1>Authors</h1>
<ul id="authors"></ul>
<script>
const ul = document.getElementById('authors');
const list = document.createDocumentFragment();
const url = 'https://jsonplaceholder.typicode.com/users';
fetch(url)
.then((response) => {
if (!response.ok) {
throw new Error(`HTTP ${response.status}`);
}
return response.json();
})
.then((authors) => {
authors.forEach((author) => {
const li = document.createElement('li');
const name = document.createElement('h2');
const email = document.createElement('span');
name.textContent = author.name;
email.textContent = author.email;
li.appendChild(name);
li.appendChild(email);
list.appendChild(li);
});
ul.appendChild(list);
})
.catch((error) => {
console.error('Fetch failed:', error);
});
</script>
Open the file in a browser. You should see ten author names and email addresses. You just completed a GET request with the JavaScript Fetch API.
fetch() defaults to GET. For POST, pass a second argument with method,
body, and headers.
const url = 'https://jsonplaceholder.typicode.com/users';
let data = {
name: 'Sammy'
};
let fetchData = {
method: 'POST',
body: JSON.stringify(data),
headers: {
'Content-Type': 'application/json'
}
};
fetch(url, fetchData)
.then((response) => {
if (!response.ok) {
throw new Error(`HTTP ${response.status}`);
}
return response.json();
})
.then((result) => {
console.log('Created:', result);
})
.catch((error) => {
console.error(error);
});
JSONPlaceholder echoes your POST body and adds an id field. In a production
API, read the status code and response body to confirm the record was saved.
The Headers interface lets you set request and response headers. On the
server side, routes map HTTP methods to handler functions. See
How To Define Routes and HTTP Request Methods in Express
for a Node.js example.
You can also build a Request and pass it to fetch():
const url = 'https://jsonplaceholder.typicode.com/users';
let data = {
name: 'Sammy'
};
let request = new Request(url, {
method: 'POST',
body: JSON.stringify(data),
headers: {
'Content-Type': 'application/json'
}
});
fetch(request)
.then((response) => response.json())
.then((result) => console.log(result));
fetch() also supports PUT, PATCH, and DELETE when you set method in
the options object.
A resolved fetch() Promise does not mean the request succeeded. The
Promise rejects only when the request cannot complete (network down, invalid
URL, aborted signal).
Check response.ok (true for status 200–299) or inspect response.status:
fetch('https://jsonplaceholder.typicode.com/posts/999')
.then((response) => {
if (!response.ok) {
return Promise.reject({
status: response.status,
statusText: response.statusText
});
}
return response.json();
})
.then((data) => console.log(data))
.catch((error) => {
console.error('Request failed:', error.status, error.statusText);
});
For async/await, throw inside try/catch when !response.ok:
async function getPost(id) {
const response = await fetch(`https://jsonplaceholder.typicode.com/posts/${id}`);
if (!response.ok) {
throw new Error(`${response.status} ${response.statusText}`);
}
return response.json();
}
getPost(1).then(console.log).catch(console.error);
Read Understanding JavaScript Promises for more on chaining and rejection.
async/await is syntactic sugar over Promises. It keeps request code flat and
easy to read:
async function fetchUsers(endpoint) {
const response = await fetch(endpoint);
if (!response.ok) {
throw new Error(`HTTP ${response.status}`);
}
const data = await response.json();
return data.map((user) => user.name);
}
fetchUsers('https://jsonplaceholder.typicode.com/users')
.then((names) => console.log(names))
.catch((error) => console.error(error));
You can return data from an async function and keep chaining .then() on
the returned Promise. For a deeper walkthrough of async/await, see
Understanding the Event Loop, Callbacks, Promises, and Async/Await in JavaScript.
Fetch has no built-in timeout. Use AbortController to cancel a request or stop
it after a deadline:
const controller = new AbortController();
const timeoutId = setTimeout(() => controller.abort(), 5000);
fetch('https://jsonplaceholder.typicode.com/users', {
signal: controller.signal
})
.then((response) => response.json())
.then((data) => {
clearTimeout(timeoutId);
console.log(data.length, 'users loaded');
})
.catch((error) => {
if (error.name === 'AbortError') {
console.error('Request timed out');
} else {
console.error(error);
}
});
AbortController is supported in current versions of Chrome, Firefox, Safari,
and Edge, and in Node.js 18+.
| Feature | Fetch API | XHR / jQuery Ajax | Axios |
|---|---|---|---|
| Installation | Native; Node 18+ | Native; needs jQuery | npm package |
| Syntax | Promise-based | Callback or Promise | Promise-based |
| JSON parsing | Manual .json() |
Manual | Automatic |
| HTTP errors | Manual response.ok |
Varies | Rejects on 4xx/5xx |
| Cancellation | AbortController |
xhr.abort() |
Cancel tokens |
| Interceptors | Not supported | Not supported | Supported |
| Interceptors | Not supported | Not supported | Supported |
For new projects that already use jQuery, read
Submitting AJAX Forms with jQuery
for a comparison of $.ajax() and fetch().
Pick Fetch when you want zero dependencies and your team is fine checking
response.ok. Pick Axios when you need interceptors, simpler error
defaults, or tighter React integration. See
How to Use Vue.js and Axios to Display Data from an API.
React apps often call fetch() inside useEffect() when a component mounts:
import { useState, useEffect } from 'react';
function App() {
const [data, setData] = useState(null);
const [error, setError] = useState(null);
useEffect(() => {
fetch('https://jsonplaceholder.typicode.com/users')
.then((response) => {
if (!response.ok) throw new Error(response.status);
return response.json();
})
.then((json) => setData(json))
.catch((err) => setError(err.message));
}, []);
if (error) return <p>Error: {error}</p>;
return <div>{data ? JSON.stringify(data) : 'Loading...'}</div>;
}
export default App;
For a React-focused walkthrough, see How to Call Web APIs with the useEffect Hook in React.
In Vue 3, call fetch() inside onMounted() or the Options API mounted() hook:
<script>
export default {
data() {
return { data: null, error: null };
},
async mounted() {
try {
const response = await fetch('https://jsonplaceholder.typicode.com/users');
if (!response.ok) throw new Error(response.status);
this.data = await response.json();
} catch (error) {
this.error = error.message;
}
}
};
</script>
Many Vue projects use Axios instead. See Vue.js REST API with Axios.
Angular ships HttpClient for most production apps. You can still call native
fetch() in a component when you want a dependency-free call:
import { Component, OnInit } from '@angular/core';
@Component({
selector: 'app-data',
template: '<p>{{ data | json }}</p>'
})
export class DataComponent implements OnInit {
data: unknown;
async ngOnInit() {
const response = await fetch('https://jsonplaceholder.typicode.com/users');
if (!response.ok) throw new Error(String(response.status));
this.data = await response.json();
}
}
The JavaScript Fetch API is a built-in interface for making HTTP requests
from browser JavaScript and from Node.js 18+. fetch() returns a Promise that
resolves to a Response object. You read the body with methods like .json()
or .text(). It replaced XMLHttpRequest for most new front-end code.
Call fetch() with the API URL, check response.ok, then parse the body:
fetch('https://jsonplaceholder.typicode.com/users')
.then((response) => {
if (!response.ok) throw new Error(response.status);
return response.json();
})
.then((data) => console.log(data))
.catch((error) => console.error(error));
The same pattern works in Node.js 18+ without extra packages. To test endpoints from the command line, see How to Use Wget to Download Files and Interact with REST APIs.
For new browser code, Fetch is the better default. It is native, Promise-based,
and does not require jQuery. Ajax (via XMLHttpRequest or $.ajax()) still
fits legacy pages that already depend on jQuery. Fetch gives you a smaller
runtime footprint and matches modern async/await style. Ajax wrappers can feel
familiar if your codebase already centers on jQuery.
Fetch does not reject on HTTP error status codes, so you must check response.ok
yourself. It does not parse JSON automatically, does not include request
interceptors, and does not report upload or download progress. Timeouts require
AbortController. For apps that need those features out of the box, a library
like Axios is often simpler.
fetch() in JavaScript?fetch() is the global function that starts a network request. The first
argument is a URL string or Request object. The optional second argument is an
options object with method, headers, body, and signal. It always returns
a Promise. The Promise resolves with response headers even when the server
returns an error code.
The JavaScript Fetch API is supported in all current major browsers and in
Node.js 18+. You can send GET and POST requests, handle HTTP errors with
response.ok, cancel slow calls with AbortController, and write cleaner code
with async/await.
For larger projects, compare Fetch with Axios or GraphQL based on how much control you need over errors, caching, and data shape. See An Introduction to GraphQL when you want clients to request only the fields they need.
Keep building with these JavaScript tutorials:
Host your API and front end on DigitalOcean App Platform with automatic deploys from GitHub. For a dedicated Node.js server, start with a Droplet and follow How to Set Up a Node.js Application for Production on Ubuntu 22.04.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
I help Businesses scale with AI x SEO x (authentic) Content that revives traffic and keeps leads flowing | 3,000,000+ Average monthly readers on Medium | Sr Technical Writer(Team Lead) @ DigitalOcean | Ex-Cloud Consultant @ AMEX | Ex-Site Reliability Engineer(DevOps)@Nutanix
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I have may be a basic question, with the url, when I work on visual studio url it’s like https://localhost:3030/api/something but when I publish it’s like https://myserver:3030/api/something how can I handle this to avoid change url in all my functions because is hardcode basically
Hey, Sara, thanks for the article. There are some minor typos in Step 2 full code so it doesn’t work. I´ve checked and change a little bit and now it´s ok:
<h1>Authors</h1>
<ul id="authors">
</ul>
<script> const ul = document.getElementById(‘authors’); const list = document.createDocumentFragment(); const url = ‘https://jsonplaceholder.typicode.com/users/’;
fetch(url) .then((response) => { return response.json(); }) .then((json) => { json.map(function(author) { let li = document.createElement(‘li’); let name = document.createElement(‘h2’); let email = document.createElement(‘span’);
name.innerHTML = `${author.name}`;
email.innerHTML = `${author.email}`;
li.appendChild(name);
li.appendChild(email);
list.appendChild(li);
ul.appendChild(list);
});
})
.catch(function(error) {
console.log(error);
});
</script>
i created an account to say this. although the article is helpful the syntax highlighting is atrocious my eyes are bleeding please change the colors please
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Scale up as you grow — whether you're running one virtual machine or ten thousand.
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.