← Glossary / Axios (Node.js)

What is Axios (Node.js)?

Q: How do I route Axios through an authenticated proxy?

Do not use the built-in proxy configuration option—it is notoriously buggy with HTTPS targets and authentication. Instead, use https-proxy-agent or socks-proxy-agent , instantiate the agent with your proxy credentials, and pass it to Axios via the httpsAgent property.

Axios (Node.js) is a popular, promise-based HTTP client used to fetch HTML or JSON payloads in JavaScript scraping scripts. While its developer experience is excellent—featuring automatic transforms and request interceptors—its default network signature is highly predictable. For production data pipelines, raw Axios is a liability unless heavily wrapped with custom TLS configurations, proxy rotation logic, and strict header management to avoid immediate bot classification.

HTTP ClientNode.jsAPI ScrapingInterceptorsStateless

// 02 — definitions

The default
fetcher.

Why the most downloaded HTTP client on npm is both the starting point for most scrapers and the first thing anti-bot systems look for.

Ask a DataFlirt engineer →

TL;DR

Axios simplifies HTTP requests in Node.js with a clean, promise-based API and built-in JSON parsing. However, its default headers and reliance on Node's standard TLS stack make it trivial for Cloudflare or DataDome to fingerprint. Production scraping requires overriding its defaults and integrating external cookie jars and proxy agents.

01Definition & structure

Axios is a promise-based HTTP client for Node.js and the browser. In a Node.js scraping context, it acts as a wrapper around the native http and https modules, providing a cleaner API for making requests, handling timeouts, and parsing responses.

A typical Axios setup involves creating an instance with baseline configurations (base URLs, default headers) and attaching interceptors to handle repetitive tasks like logging or proxy assignment.

02Interceptors for scraping

The primary reason engineers choose Axios over native fetch is the interceptor model. Interceptors are middleware functions that run before a request is sent or after a response is received.

In scraping pipelines, request interceptors are used to dynamically inject rotating proxy credentials or fresh User-Agent strings. Response interceptors are used to catch 403 Forbidden or 429 Too Many Requests errors, trigger a proxy rotation, and automatically retry the request without failing the main execution thread.

03The fingerprinting problem

Out of the box, Axios is extremely loud. It sends an Accept: application/json, text/plain, */* header and an axios/1.x.x User-Agent. Even if you spoof the User-Agent to look like Chrome, the underlying Node.js TLS handshake (JA3 fingerprint) remains unchanged.

Anti-bot systems look for this mismatch: a client claiming to be Chrome 124 but negotiating TLS like a Node.js script. This results in an immediate block or CAPTCHA challenge.

04Managing state and cookies

Unlike a browser, Axios is stateless. If a server sets a cookie via the Set-Cookie header, Axios will not automatically send it back on the next request. For scraping targets that require session persistence or CSRF tokens, you must manually parse and attach cookies, or use a wrapper library.

The standard pattern is to use axios-cookiejar-support wrapped around a tough-cookie instance, which mimics browser-like cookie storage and expiration logic.

05Did you know?

Using Axios's built-in proxy configuration object is a known anti-pattern for HTTPS targets. Due to historical bugs in how Axios handles CONNECT tunnels for HTTPS, the community standard is to disable the built-in proxy config entirely (proxy: false) and instead pass a dedicated tunneling agent like https-proxy-agent to the httpsAgent property.

// 03 — the interceptor model

How much overhead
does Axios add?

Axios adds a slight abstraction layer over Node's native HTTP module. When scaling to thousands of requests per second, connection pooling and interceptor execution time become measurable constraints.

Effective request latency = L = T_dns + T_tls + T_ttfb + T_interceptors

Interceptors run synchronously before and after the network call. Node.js Event Loop Profiling

Connection pool utilization = U = Active_Sockets / Max_Sockets

Node's default maxSockets is Infinity, which can exhaust ephemeral ports if unbound. Node.js http.Agent

Retry backoff delay = D = Base_Delay × 2^Attempt + Jitter

Standard implementation used in plugins like axios-retry. Network Reliability Patterns

// 04 — the network trace

A default Axios request,
flagged at the edge.

What happens when a junior engineer runs axios.get() against a protected target. The edge immediately identifies the Node.js runtime and default Axios headers.

Node.js TLSDefault HeadersHTTP/1.1

edge.dataflirt.io — live

CAPTURED

// outbound request
GET /api/v1/pricing HTTP/1.1
Host: target.com
Accept: application/json, text/plain, */* // axios default
User-Agent: axios/1.6.8 // fatal giveaway

// edge inspection
tls.ja3: "771,4865-4866-4867..." // Node.js signature
header.order: [Host, Accept, User-Agent] // non-browser order

// response
HTTP/1.1 403 Forbidden
Server: cloudflare
cf-ray: 88a7f...
body: "Please enable JavaScript to view this page."

// 05 — detection vectors

Why raw Axios
fails in production.

The specific signals that anti-bot vendors use to classify an Axios request as automated traffic, ranked by how frequently they trigger blocks across our monitored targets.

TARGETS MONITORED · · 300+ active

WINDOW · · · · · · 30d trailing

UPDATED · · · · · · 2026-05-19

Default User-Agent

fatal signal · axios/1.x.x guarantees an immediate block

Node.js TLS Fingerprint

network layer · JA3/JA4 mismatch with advertised browser UA

Header Order

http layer · Node's http module alphabetizes or uses specific orders

Missing Accept-Language

http layer · Browsers always send locale preferences; Axios does not

HTTP/2 Pseudo-header order

http/2 layer · Node's http2 module defaults differ from Chrome

// 06 — production hardening

Wrap it, patch it,

or abandon it for a better stack.

At DataFlirt, we rarely use raw Axios for external scraping. When we do use Node.js for API ingestion, Axios is heavily wrapped. We inject custom https.Agent configurations to spoof TLS signatures, enforce strict header dictionaries that match real browser profiles, and use interceptors to route traffic through our residential proxy gateways with automatic retry-and-rotate logic on 403s.

axios.create() config

A hardened Axios instance ready for API scraping.

httpsAgent CustomTLSAgentja3-spoofed

headers.User-Agent Mozilla/5.0 (Macintosh...rotated

headers.Accept text/html,application/xhtml+xml...

proxy falseusing tunnel agent

interceptors.resp rotate_on_403active

timeout 15000ms

Stay ahead of the pipeline

Data engineering
intel, weekly.

Anti-bot shifts, scraping infrastructure updates, dataset delivery patterns, and business outcomes from our pipelines. Short, technical, no fluff.

// 07 — FAQ

Common
questions.

About Axios configuration, proxy routing, TLS fingerprinting, and why native fetch is replacing it in modern Node environments.

Ask us directly →

Why use Axios instead of native fetch in Node.js? +

Axios provides request and response interceptors, automatic JSON transformation, and a massive ecosystem of plugins like axios-retry. While Node 18+ includes native fetch, Axios's interceptor model makes it much easier to build complex proxy rotation and error-handling middleware for scraping pipelines.

How do I handle cookies in Axios? +

Axios is stateless by default. It does not remember cookies between requests. To maintain a session, you must integrate a third-party library like axios-cookiejar-support alongside tough-cookie, and attach the jar to your Axios instance.

Can Axios bypass Cloudflare or DataDome? +

Not on its own. Cloudflare detects the underlying Node.js TLS fingerprint before Axios even sends HTTP headers. To bypass advanced anti-bot systems, you must pass a custom https.Agent that modifies the TLS handshake, or route the Axios request through a proxy network that handles TLS termination for you.

How do I route Axios through an authenticated proxy? +

Do not use the built-in proxy configuration option—it is notoriously buggy with HTTPS targets and authentication. Instead, use https-proxy-agent or socks-proxy-agent, instantiate the agent with your proxy credentials, and pass it to Axios via the httpsAgent property.

How does DataFlirt use Axios? +

We primarily use Axios for internal microservice communication, webhook delivery, and interacting with our clients' REST APIs. For external data extraction against hostile targets, we prefer Go-based fetchers or headless browsers, which offer much deeper control over the network stack and rendering engine.

What is the best way to handle rate limits with Axios? +

Use a response interceptor. When Axios receives a 429 Too Many Requests status, the interceptor should catch the error, read the Retry-After header from the response, pause execution for the specified duration, and then automatically re-queue the original request.

$ dataflirt scope --new-project --target=axios-(node.js) READY

Tell us what
to extract.
We do the rest.

20-minute scoping call. Pilot dataset within the week. Production within two. Whether you need a one-off catalogue dump or a continuous feed across millions of records — we scope, build, and operate the pipeline.

Start a pipeline → View pricing

hello@dataflirt.com · Bengaluru · IST · typical reply < 4h

What is Axios (Node.js)?

The defaultfetcher.

TL;DR

How much overheaddoes Axios add?

A default Axios request,flagged at the edge.

Why raw Axiosfails in production.

Default User-Agent

Node.js TLS Fingerprint

Header Order

Missing Accept-Language

HTTP/2 Pseudo-header order

Wrap it, patch it,

axios.create() config

Stay ahead of the pipeline

Data engineeringintel, weekly.

Commonquestions.

Tell us whatto extract.We do the rest.

Related glossary terms

Cheerio (Node.js)

TLS Fingerprinting

HTTP Headers

Connection Pooling