Request inspection with httpbin-compatible paths: echo any method, read your headers and IP, delay a response, chain redirects, test Basic and Bearer auth, ETags and cache headers.
Base URL: https://funapi.dev/api/echo/v1 · 26 endpoints · OpenAPI 3.1 spec and Postman collection available. New here? Read the getting started guide.
request
GET /echo/v1/anything — Echo a GET: method, query, headers, body and origin · Responds with 200 Link to this endpointGET /echo/v1/get — httpbin-style /get — same echo, GET only · Responds with 200 405 Link to this endpointPOST /echo/v1/anything — Echo a POST: method, query, headers, body and origin · Responds with 200 Link to this endpointPOST /echo/v1/post — httpbin-style /post — same echo, POST only · Responds with 200 405 Link to this endpointPUT /echo/v1/anything — Echo a PUT: method, query, headers, body and origin · Responds with 200 Link to this endpointPUT /echo/v1/put — httpbin-style /put — same echo, PUT only · Responds with 200 405 Link to this endpointPATCH /echo/v1/anything — Echo a PATCH: method, query, headers, body and origin · Responds with 200 Link to this endpointPATCH /echo/v1/patch — httpbin-style /patch — same echo, PATCH only · Responds with 200 405 Link to this endpointDELETE /echo/v1/anything — Echo a DELETE: method, query, headers, body and origin · Responds with 200 Link to this endpointDELETE /echo/v1/delete — httpbin-style /delete — same echo, DELETE only · Responds with 200 405 Link to this endpointGET /echo/v1/headers — The request headers the server received · Responds with 200 Link to this endpointGET /echo/v1/ip — The caller IP as seen by the server · Responds with 200 Link to this endpointGET /echo/v1/user-agent — The User-Agent header · Responds with 200 Link to this endpointtiming
GET /echo/v1/delay/{seconds} — Respond after 0–10 seconds — test client timeouts · Responds with 200 400 Link to this endpointstatus
GET /echo/v1/status/{code} — Return the status code you ask for (200–599) · Responds with 200 400 Link to this endpointredirects
GET /echo/v1/redirect/{n} — Redirect n times (302 chain), then echo · Responds with 302 400 Link to this endpointauth
GET /echo/v1/basic-auth/{user}/{password} — HTTP Basic auth: 200 when the credentials match the path, 401 otherwise · Responds with 200 401 Link to this endpointGET /echo/v1/bearer — Any Bearer token → 200; none → 401 with WWW-Authenticate · Responds with 200 401 Link to this endpointdata
GET /echo/v1/uuid — A random UUID v4 · Responds with 200 Link to this endpointGET /echo/v1/base64/{value} — Decode a base64 / base64url value · Responds with 200 400 Link to this endpointformats
GET /echo/v1/json — A fixed JSON document · Responds with 200 Link to this endpointGET /echo/v1/xml — A fixed XML document (application/xml) · Responds with 200 Link to this endpointGET /echo/v1/stream/{n} — n newline-delimited JSON objects (application/x-ndjson) · Responds with 200 400 Link to this endpointcaching
GET /echo/v1/etag/{etag} — Responds with your ETag; If-None-Match → 304, mismatched If-Match → 412 · Responds with 200 304 412 Link to this endpointGET /echo/v1/cache/{seconds} — Sets Cache-Control: private, max-age=seconds (browser caching only) · Responds with 200 400 Link to this endpointGET /echo/v1/response-headers — Echo query pairs back as response headers (X-* and a few safe names) · Responds with 200 400 Link to this endpointThe HTTP Echo & Inspect API answers the question every HTTP client test eventually asks: what did the server actually receive? It follows the httpbin path conventions — /anything, /get, /headers, /ip, /delay, /status, /redirect, /basic-auth, /bearer — so scripts written for httpbin keep working with a new base URL, and it runs on the same infrastructure as the rest of the catalog when you need it in CI.
GET https://funapi.dev/api/echo/v1/anything — Echo a GET: method, query, headers, body and origin. No token, no signup:
curl -i https://funapi.dev/api/echo/v1/anything
Response: 200 OK
{
"method": "GET",
"args": {},
"json": null,
"data": "",
"headers": {
"note": "The in-browser simulator does not see real request headers. Call the live API to inspect them."
},
"origin": "browser-simulator",
"url": null
}
Last updated