The request URI is longer than the server is willing to interpret, usually because too much data went into the query string.
Defined in RFC 9110 §15.5.15 — 414 URI Too Long · MDN reference
Search and filter endpoints that put long lists of IDs in the query, GET requests that should have been POSTs, redirect loops that append to the URL each time, and SSO flows carrying large tokens.
Generate a query string with thousands of IDs and see where your stack breaks. The limit is rarely the server's alone: proxies, CDNs and browsers each have one.
Move the data into a request body — a POST to a search endpoint is the conventional answer. Do not split the request blindly; filters often have to apply together.
1 endpoint in this playground answers with 414. Every one is free, needs no signup, and can be called from the browser or with curl.
GET https://funapi.dev/api/faults/v1/status/{code} — Return any status code on demand (200–599) (Fault Injection API) Open & run this endpointAll HTTP status codes · All 39 mock REST APIs · Getting started guide
Last updated