Limits: Can Axios Interceptors Enforce Pagination Limits on Large API Responses?

Answer

Yes, a request interceptor can modify the outgoing config to inject or cap limit and offset query parameters before the HTTP call is sent. This bounds the amount of data the client requests, but it does not stop the server from ignoring those parameters or returning more data. A transformResponse hook can only trim the payload after it arrives.

Confirmed facts

• Axios request interceptors receive the config object and can change config.params or config.data before dispatch.
• A global interceptor attached to the default axios instance runs for every request unless an instance has its own interceptor chain that shadows it.
• Cloning config.params before mutation avoids side effects on retry logic or other interceptors.

Likely explanation / pattern

Create a reusable interceptor that:

1. Clones config.params.
2. Ensures a limit value exists, defaulting to a configured value.
3. Caps the value at a maximum allowed size.
4. Adds an offset of 0 when missing (for offset‑based pagination).
5. Returns the modified config.

Example implementation:

function paginationLimitInterceptor({ maxLimit = 200, defaultLimit = 50 } = {}) {
  return function (config) {
    if (!config.params) config.params = {};
    const params = { ...config.params };
    const limit = Number(params.limit) || defaultLimit;
    params.limit = Math.min(limit, maxLimit);
    if (!('offset' in params)) params.offset = 0;
    config.params = params;
    return config;
  };
}

Attach it to an instance:

const api = axios.create({ baseURL: 'https://example.com/api' });
api.defaults.maxLimit = 100;
api.interceptors.request.use(paginationLimitInterceptor({ maxLimit: 100 }));

Per‑module limits

• Use separate Axios instances, each with its own maxLimit and interceptor.
• Or pass a custom marker in the request config (e.g., config._paginationLimit) that the interceptor reads to override the global default.

transformResponse

The transformResponse hook runs after the server replies. It can slice or discard items that exceed the desired limit, but it cannot prevent the server from sending the full payload. It is useful as a safety net when the API is unreliable.

Missing diagnostic detail

To tailor the interceptor precisely, we need to know whether the target API uses offset/limit pagination or a cursor/keyset scheme. If a cursor is required, injecting limit/offset may be ignored or cause errors, so the interceptor should be endpoint‑specific or disabled for those routes.