Apidog

All-in-one Collaborative API Development Platform

API Design

API Documentation

API Debugging

API Mocking

API Automated Testing

Axios vs Fetch: Which is Best for HTTP Requests

There are many ways to make HTTP requests in JavaScript, but two of the most popular ones are Axios and fetch(). In this post, we will compare and contrast these two methods and see which one is best for different scenarios.

Ashley Innocent

Ashley Innocent

Updated on November 12, 2024

HTTP requests are essential for communicating with servers and APIs in web applications. There are many ways to make HTTP requests in JavaScript, but two of the most popular ones are Axios and fetch(). In this post, we will compare and contrast Axios and Fetch() and see which one is best for different scenarios.

button

What is Axios?

Axios is a third-party library that provides a promise-based HTTP client for making HTTP requests. Axios is widely used in the JavaScript community and is known for its simplicity and flexibility

Basic Syntax of Axios

The basic syntax of the Axios library is as follows:

axios(config)
  .then(response => console.log(response.data))
  .catch(error => console.error('Error:', error));

Key features:

  1. Can accept an object containing both URL and configuration as a parameter, or separate URL and configuration object.
  2. Uses the data property to send data to the server, automatically handling JSON conversion.
  3. Returns server data directly in the data property of the response object.
  4. Automatically handles HTTP error status codes, passing them to the catch block.
  5. Provides a more streamlined error handling mechanism.

Example:

axios({
  method: 'post',
  url: 'https://api.example.com/data',
  data: {
    key: 'value'
  }
})
  .then(response => console.log(response.data))
  .catch(error => {
    if (error.response) {
      console.error('Server responded with:', error.response.status);
    } else if (error.request) {
      console.error('No response received');
    } else {
      console.error('Error:', error.message);
    }
  });

Why should You Use Axios?

It has many features that make it easy and convenient to use, such as:

  • Automatic JSON data transformation: Axios automatically converts the data to and from JSON, so you don’t have to manually parse or stringify it.
  • Response timeout: Axios allows you to set a timeout for your requests, so you can handle errors if the server takes too long to respond.
  • HTTP interceptors: Axios lets you intercept requests and responses before they are handled by then or catch, so you can modify them or add additional logic.
  • Download progress: Axios can track the progress of your downloads and uploads, so you can display feedback to the user or cancel the request if needed.
  • Simultaneous requests: Axios can make multiple requests at the same time and combine them into a single response using axios.all and axios.spread.

What is Fetch()?

fetch() is a built-in API that comes with native JavaScript. It is an asynchronous web API that returns the data in the form of promises. fetch() is supported by all modern browsers, so you don’t need to import any external library to use it. Some of the features of fetch() are:

  • Basic syntax: fetch() has a simple and concise syntax that takes the URL of the resource you want to fetch as the first argument and an optional options object as the second argument.
  • Backward compatibility: fetch() can be used in older browsers that don’t support it by using a polyfill, such as whatwg-fetch or fetch-ponyfill.
  • Customizable: fetch() gives you more control over your requests and responses, as you can customize the headers, body, method, mode, credentials, cache, redirect, and referrer policies.
How to Use the Fetch APIs in React?
React, a popular JavaScript library for building user interfaces, provides a straightforward way to fetch data from APIs. In this guide, we’ll explore the process of fetching data from an API in a React, accompanied by a practical example.

How to Use Axios to Make HTTP Requests?

To use Axios, you need to install it using npm or yarn:

npm install axios

And here’s how to install Axios using yarn:

yarn add axios

If you prefer to use pnpm, you can install Axios using the following command:

pnpm install axios

Alternatively, you can use a content delivery network (CDN) to include Axios in your project. Here’s how to include Axios using a CDN:

<script src="https://unpkg.com/axios/dist/axios.min.js"></script>

Then, you can import it in your JavaScript file and use it to make HTTP requests. For example, to make a GET request to a URL, you can use axios.get():

import axios from 'axios';

axios.get('https://example.com/api')
  .then(response => {
    console.log(response.data);
  })
  .catch(error => {
    console.error(error);
  });
How to make HTTP requests with Axios in 2024
Learn how to make HTTP requests like a pro with Axios. This tutorial covers everything you need to know about using Axios to make HTTP requests, including how to make an Axios POST request with axios.post().

Making HTTP Requests with Fetch

To use fetch(), you don’t need to install anything, as it is already available in the browser. You can use the fetch() function to make HTTP requests. For example, to make a GET request to a URL, you can use fetch() like this:

fetch('https://example.com/api')
  .then(response => {
    return response.json();
  })
  .then(data => {
    console.log(data);
  })
  .catch(error => {
    console.error(error);
  });

Notice that:

  • Axios automatically transforms the data to and from JSON, while fetch() requires you to call response.json() to parse the data to a JavaScript object.
  • Axios provides the data in the response object, while fetch() provides the response object itself, which contains other information such as status, headers, and url.
  • Axios handles errors in the catch block, while fetch() only rejects the promise if there is a network error, not if the response has an error status.

Basic Syntax of Fetch

Certainly. I'll provide the content in English, organized into two separate parts as requested.

The basic syntax of the Fetch API is as follows:

fetch(url, options)
  .then(response => response.json())
  .then(data => console.log(data))
  .catch(error => console.error('Error:', error));

Key features:

  1. URL as the first argument, optional configuration object as the second argument.
  2. Uses the body property to send data to the server, requiring manual conversion of data to string.
  3. Returns a Response object containing complete response information.
  4. Only enters the catch block on network errors, not on HTTP error status codes.
  5. Requires manual checking of response status codes to handle HTTP errors.

Example:

fetch('https://api.example.com/data', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ key: 'value' })
})
  .then(response => {
    if (!response.ok) {
      throw new Error('HTTP error ' + response.status);
    }
    return response.json();
  })
  .then(data => console.log(data))
  .catch(error => console.error('Error:', error));

Axios vs Fetch: Sending a GET Request with Query Parameters:

// Axios
axios.get('/api/data', {
  params: {
    name: 'Alice',
    age: 25
  }
})
.then(response => {
  // handle response
})
.catch(error => {
  // handle error
});

// Fetch
const url = new URL('/api/data');
url.searchParams.append('name', 'Alice');
url.searchParams.append('age', 25);

fetch(url)
.then(response => response.json())
.then(data => {
  // handle data
})
.catch(error => {
  // handle error
});

Axios vs Fetch: Sending a POST Request with a JSON Body:

// Axios
axios.post('/api/data', {
  name: 'Bob',
  age: 30
})
.then(response => {
  // handle response
})
.catch(error => {
  // handle error
});

// Fetch
fetch('/api/data', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    name: 'Bob',
    age: 30
  })
})
.then(response => response.json())
.then(data => {
  // handle data
})
.catch(error => {
  // handle error
});

Axios vs Fetch: Setting a Timeout for the Request:

// Axios
axios.get('/api/data', {
  timeout: 5000 // 5 seconds
})
.then(response => {
  // handle response
})
.catch(error => {
  // handle error
});

// Fetch
const controller = new AbortController();
const signal = controller.signal;

setTimeout(() => {
  controller.abort(); // abort after 5 seconds
}, 5000);

fetch('/api/data', { signal })
.then(response => response.json())
.then(data => {
  // handle data
})
.catch(error => {
  // handle error
});

Axios vs Fetch: Using async/await syntax:

// Axios
async function getData() {
  try {
    const response = await axios.get('/api/data');
    // handle response
  } catch (error) {
    // handle error
  }
}

// Fetch
async function getData() {
  try {
    const response = await fetch('/api/data');
    const data = await response.json();
    // handle data
  } catch (error) {
    // handle error
  }
}

Axios vs Fetch: Backward Compatibility

Backward compatibility refers to the ability of a newer system or application to work with old versions, ensuring a smooth transition and prevention of disruptions or breakages when upgrading. It is crucial in software development, web development, and technology ecosystems to maintain stability, compatibility, and consistent versions and platforms.

Axios:

  • Axios is a third-party library that needs to be installed and included in your project.
  • It supports older browsers by including polyfills for promises and other modern JavaScript features.
  • Axios is actively maintained and keeps up with the latest browser and Node.js updates, ensuring compatibility with new environments.
  • However, since it's a separate library, you need to ensure that you're using a compatible version with your project dependencies.

Fetch:

  • The Fetch API is a native Web API supported by modern browsers.
  • It has excellent support in recent browser versions, but older browsers (such as Internet Explorer) do not support it natively.
  • If you need to support older browsers, you'll need to include a polyfill or use a fallback solution (e.g., XMLHttpRequest).
  • Since it's a native API, it's automatically updated and maintained by browser vendors, ensuring compatibility with future browser versions.

Axios vs Fetch: Error Handling

Error handling is an important aspect of making HTTP requests, as it allows you to handle different scenarios such as network failures, server errors, or invalid responses. Fetch and Axios have different ways of handling errors, which I will compare with some examples.

Axios:

In Axios, if there is a request failure, it throws an error and you can easily handle the error with a try-catch block and get the error data from error.response.data. For example:

// Axios error handling with try-catch
try {
  const response = await axios.get('/api/data');
  // handle response
} catch (error) {
  // handle error
  console.log(error.response.data);
}

Fetch:

In Fetch, if there is a request failure, it does not throw an error, but returns a response object with an ok property set to false. You have to check the ok property and throw an error manually if you want to use a try-catch block.

Alternatively, you can use the response.ok property to handle different cases in the then method. For example:

// Fetch error handling with try-catch
try {
  const response = await fetch('/api/data');
  // check response status
  if (!response.ok) {
    // throw error if status is not ok
    throw new Error(`HTTP error! status: ${response.status}`);
  }
  // handle response
} catch (error) {
  // handle error
  console.log(error.message);
}

// Fetch error handling with response.ok
fetch('/api/data')
  .then(response => {
    // check response status
    if (response.ok) {
      // handle response
    } else {
      // handle error
      console.log(`HTTP error! status: ${response.status}`);
    }
  })
  .catch(error => {
    // handle network error
    console.log(error.message);
  });

Another difference between Fetch and Axios is how they handle non-200 status codes. Axios considers any status code outside the range of 2xx as an error and rejects the promise. Fetch considers any valid HTTP response (even 4xx or 5xx) as a success and resolves the promise.

This means that you have to handle non-200 status codes differently in Fetch and Axios. For example:

// Axios error handling for non-200 status codes
axios.get('/api/data')
  .then(response => {
    // handle response
  })
  .catch(error => {
    // handle error
    if (error.response) {
      // server responded with a status code outside 2xx
      console.log(error.response.status);
      console.log(error.response.data);
    } else {
      // network error or request was aborted
      console.log(error.message);
    }
  });

// Fetch error handling for non-200 status codes
fetch('/api/data')
  .then(response => {
    // check response status
    if (response.ok) {
      // handle response
    } else {
      // server responded with a status code outside 2xx
      console.log(response.status);
      return response.json();
    }
  })
  .then(data => {
    // handle error data
    console.log(data);
  })
  .catch(error => {
    // handle network error or request was aborted
    console.log(error.message);
  });

Axios vs Fetch: Which is Best for Making HTTP Requests?

There is no definitive answer to which one is better, as it depends on your preferences and needs. However, here are some general guidelines to help you decide:

  • Use Axios if you want a simple and convenient way to make HTTP requests, with features such as automatic JSON data transformation, response timeout, HTTP interceptors, download progress, and simultaneous requests.
  • Use fetch() if you want a native and customizable way to make HTTP requests, with features such as backward compatibility, custom headers, body, method, mode, credentials, cache, redirect, and referrer policies.

Generate Axios/Fetch Code with Apidog

Apidog is an all-in-one collaborative API development platform that provides a comprehensive toolkit for designing, debugging, testing, publishing, and mocking APIs. Apidog enables you to automatically create Axios code for making HTTP requests.

button

Here's the process for using Apidog to generate Axios code:

Step 1: Open Apidog and select new request

Create New Request

Step 2: Enter the URL of the API endpoint you want to send a request to,input any headers or query string parameters you wish to include with the request, then click on the "Design" to switch to the design interface of Apidog.

Step 3: Select "Generate client code " to generate your code.

Generate client code

Step 4: Copy and paste the generated Axios code into your project.

Axios code

Using Apidog to Send HTTP Requests

Apidog offers several advanced features that further enhance its ability to test HTTP requests. These features allow you to customize your requests and handle more complex scenarios effortlessly.

button

Step 1: Open Apidog and create a new request.

Apidog

Step 2: Find or manually input the API details for the POST request you want to make.

POST request

Step 3: Fill in the required parameters and any data you want to include in the request body.

Apidog POST parameters and Response

Conclusion

Both Axios and fetch() are powerful and reliable methods for making HTTP requests in JavaScript. You can choose the one that suits your project and style better, or even use both of them for different purposes. The important thing is to understand how they work and how to use them effectively.

Using  Apidog not only saves you valuable time and effort but also ensures that your code is accurate and error-free. With its user-friendly interface and intuitive features, Apidog is a must-have tool for any developer working with Axios requests. Happy coding!

button

Best API Monitoring Tools 2025 (Free & Paid Services)Viewpoint

Best API Monitoring Tools 2025 (Free & Paid Services)

These digital conduits facilitate a symphony of interactions between disparate software systems, enabling them to converse, collaborate, and co-create the seamless digital experiences we've come to rely on daily.

Habibur Rahman

December 18, 2024

Best Stoplight Studio AlternativesViewpoint

Best Stoplight Studio Alternatives

Get to know the many alternatives to Stoplight Studio. This curated list of options are all worth a try!

Steven Ang Cheong Seng

December 18, 2024

7 Excellent API Documentation Examples for 2025Viewpoint

7 Excellent API Documentation Examples for 2025

Good documentation can significantly ease the learning curve and enhance the developer experience. Today, we're diving into eight remarkable examples of API documentation from successful companies, showcasing their unique approaches and best practices.

Habibur Rahman

December 18, 2024