Setting Up Axios Interceptors For HTTP Calls With Refresh Token

A modern & popular promise-based HTTP client which we use to perform HTTP requests is Axios. It supports all modern browsers, including the old ones also. It allows users to make XMLHttpRequests interact with servers. Also allows request and response interception, allows users to set response timeout, Offers protection against XSRF at the client-side, Supports the Promise API, Allows request cancellation, Allows request and response data transformation, and Offers automatic transformation for JSON data.

Axios have many other features, including configuration defaults, error handling, canceling of requests, serializing JavaScript objects to JSON automatically, and many more. In this article, we will learn to set up axios interceptor for HTTP calls with the refresh token.

Installation

# Using NPM
npm install --save axios

# Using Yarn
yarn add axios

What Is An Interceptor?

Generally, an interceptor is a function called for every HTTP request, and the application receives the response. In another word, the Axios interceptor is a function called by Axios to update/transform each request before forwarding it & check/filter the response before returning it. In short, you can intercept the requests or responses before they are handled by then or caught.

Before being handled by the .then() or the .catch(), interceptors have a feature that allows an application to intercept requests or responses.
To access data, every HTTP request needs a header property to verify the application requesting data is allowed.

Sometimes the returned HTTP response is a 400 or 500 Bad Response Code status. At those times, you might want to automatically retry the request or verify that the rejected authorization is still valid.

Intercepting Requests

The below example shows how to set up an Axios request interceptor. Generally, two functions accept an Axios interceptor. If it’s a valid, successful request the first function of the request interceptor modifies the request, and the second function works when the request is invalid and throws an error, etc.

Mainly use of this particular interceptor is whenever the application makes an HTTP request to one of the supporting service’s URLs. Axios robotically attaches a header to the request with the username kept within the state. If the HTTP request isn’t always approximately going to one of the services, the interceptor does not do anything to alter the request and lets it cross on its way unaltered.

In some cases, if the request is malformed, the second error() function will start in and throw an error rejecting the request, which gives why it happens.

Axios is importing at the top of the file with ES6 import syntax, and it’s ready to be used. Here we are using ES6 arrow functions in this example.

Intercepting Requests

Create Axis Instance

Create Axis Instance

Axios Request Interceptor Example

Axios Request Interceptor Example

Intercepting Responses

There are two perform arguments within response interceptors that it accept. The primary function is once the response comes back, maybe a 200 or 201 status code HTTP response, and therefore the second function is when it’s a standing status code that falls outside of the 200 or 201 status code range.

An HTTP response comes returned from a service with a 401 unauthorized error; therefore, the motive is that the primary argument handed interior to the response interceptor is undefined. If the response is some 200 responses, the Axios interceptor doesn’t care.

If the HTTP response is 401, the secondary function (originalRequestRetry() function) is triggered and checks if the logged-in user’s credentials are still valid since a 401 indicates the user’s authorization token, cookie, or session user has expired. Suppose the user’s session has indeed expired.

In that case, the session will be terminated by the application logging the user out and prompting them to log in again if that is not the reason for the 401, and the user will be able to continue their session.

Sometimes there was throwing internal server error in which status codes were 500/ 501/502/503. In this situation, we must show a message through an internal server error message inside the application.

Hire React Native Developers

Axios Response Interceptor Example

Axios Response Interceptor Example

If the request fails again and the server continues to come back with the 401 status code, it will head to the Infinite loop. For handling this, we tend to use a flag decision _retry on the initial Request (config). _retry is about to true right the first time we meet 401 status.

Refresh Token

Refresh token means when our request failed with status code 401 at this time, applications show an error and do not run at that time due to Session Timeout.

For that issue, we have issued refresh_Token by calling our reAuth API and got our new access_token by giving the device_token to the API.

Full Example For Getting Refresh token

Full Example For Getting Refresh token

HTTPService Call

By this HttpService call, we have to give the API_URL and params, which are used to call our API for getting data and showing it to our application or post from our application. In this HttpService call, we have to write our Axios function, which calls CRUD operation to create/post, read/get, update, and delete.

On there, we are already given our header in the interceptor, so we don’t need all of these. We have only to pass our parameters to get our responses.

Full Example Of An HTTPService

Full Example Of An HTTPService

In this below function, we are passing our API_URL and necessary required params to the function, and by giving that API_URL and params. This gives responses and errors.

So in our action, we have to get our responses to pass our components. When response status code 200 or 201 at that time, we know that the API call was a success, and by succeeding in this API call, we are getting our required responses for use.

Below Example Of An HTTP Service Component

Example Of An HTTP Service Component

coma

Conclusion

In this blog, we saw how we could use the Axios interceptor functions to intercept every request, update the request with authorization header, API key, etc. If everything is set up like this, we can forward the request. Once the request is resolved, take the response, and perform operations inside the application.

Satyabrata

Tech Expert

Satyabrata is a React Native Developer with around 2+ years of experience in developing mobile applications. Skills like developing clean and reusable code, Creating responsive Mobile pages, API integration etc. 

Get in touch for a detailed discussion.

Hear From Our 100+ Customers
coma

Mindbowser helped us build an awesome iOS app to bring balance to people’s lives.

author
ADDIE WOOTTEN
CEO, SMILINGMIND
coma

We had very close go live timeline and MindBowser team got us live a month before.

author
Shaz Khan
CEO, BuyNow WorldWide
coma

They were a very responsive team! Extremely easy to communicate and work with!

author
Kristen M.
Founder & CEO, TotTech
coma

We’ve had very little-to-no hiccups at all—it’s been a really pleasurable experience.

author
Chacko Thomas
Co-Founder, TEAM8s
coma

Mindbowser is one of the reasons that our app is successful. These guys have been a great team.

author
Dave Dubier
Founder & CEO, MangoMirror
coma

Mindbowser was very helpful with explaining the development process and started quickly on the project.

author
Hieu Le
Executive Director of Product Development, Innovation Lab
coma

The greatest benefit we got from Mindbowser is the expertise. Their team has developed apps in all different industries with all types of social proofs.

author
Alex Gobel
Co-Founder, Vesica
coma

Mindbowser is professional, efficient and thorough. 

author
MacKenzie R
Consultant at XPRIZE
coma

Very committed, they create beautiful apps and are very benevolent. They have brilliant Ideas.

author
Laurie Mastrogiani
Founder, S.T.A.R.S of Wellness
coma

MindBowser was great; they listened to us a lot and helped us hone in on the actual idea of the app.” “They had put together fantastic wireframes for us.

author
Bennet Gillogly
Co-Founder, Flat Earth
coma

They're very tech-savvy, yet humble.

author
Uma Nidmarty
CEO, GS Advisorate, Inc.
coma

Ayush was responsive and paired me with the best team member possible, to complete my complex vision and project. Could not be happier.

author
Katie Taylor
Founder, Child Life On Call
coma

As a founder of a budding start-up, it has been a great experience working with Mindbower Inc under Ayush's leadership for our online digital platform design and development activity.

author
Radhika Kotwal
Founder of Courtyardly
coma

The team from Mindbowser stayed on task, asked the right questions, and completed the required tasks in a timely fashion! Strong work team!

author
Michael Wright
Chief Executive Officer, SDOH2Health LLC
coma

They are focused, patient and; they are innovative. Please give them a shot if you are looking for someone to partner with, you can go along with Mindbowser.

author
David Cain
CEO, thirty2give
coma

We are a small non-profit on a budget and they were able to deliver their work at our prescribed budgets. Their team always met their objectives and I'm very happy with the end result. Thank you, Mindbowser team!!

author
Bart Mendel
Founder, Mindworks
coma

Mindbowser was easy to work with and hit the ground running, immediately feeling like part of our team.

author
George Hodulik
CEO, Stealth Startup, Ex-Google