Lightweight in-browser HTTP debugger, like a mini Postman.

Switch tool

Response

Send a request to see the response here.

How to use

Purpose

Online HTTP/REST API client that makes GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS requests from the browser, with Headers/Query/Body (JSON/Form/Raw) and Authentication (Basic/Bearer/API Key). The response panel shows status code, response headers, body (JSON auto-formatted, HTML rendered, images previewed), and timing. Supports environment variables, request history, and one-click code snippets for curl/fetch/axios/Postman. All requests originate from the browser, no third-party proxy. Common for REST API debugging, frontend-backend integration, tutorial demos, and API doc examples.

Steps

Pick method: GET (default), POST, PUT, PATCH, DELETE, HEAD, OPTIONS
Type the URL (supports env vars {{ baseUrl }})
Query tab: query parameters (auto URL-encoded)
Headers tab: common Content-Type / Authorization one-click insert
Body tab: pick type (JSON / Form Data / URL Encoded / Raw / Binary)
Auth tab: Basic / Bearer / API Key — three mainstream methods
Click Send; right pane shows live response
Generate code: one-click copy curl / fetch / axios / Postman formats

FAQ

How to fix browser CORS errors?: CORS is a browser security mechanism: when JS in domain A requests an API in domain B, B must return Access-Control-Allow-Origin. Workarounds: 1) browser extension (CORS Unblock); 2) Postman/desktop tools (no CORS); 3) backend adds CORS header; 4) proxy (dev server proxy / nginx forwarding). This tool is browser-based and subject to CORS.
How to fill in Bearer Token?: In Auth tab pick "Bearer Token" and paste the JWT or access_token (no "Bearer " prefix — tool prepends). Corresponding header: Authorization: Bearer eyJhbGc... If you do not have a token: call /token first to obtain access_token.
POST form-data vs JSON body?: Form Data: Content-Type application/x-www-form-urlencoded or multipart/form-data, params like query string (a=1&b=2) — default HTML form submission. JSON Body: application/json, body is a JSON string — modern REST API default. File upload: must be multipart/form-data (JSON cannot carry binary).
How to test endpoints that require login?: Cookie: log into the target site in your browser; cookies attach automatically (same origin only). Token: call login endpoint, copy access_token to Auth Bearer. Session: like cookie, same origin only. This tool is best for Token APIs; cookie/session is limited to same-origin scenarios.
How to test file upload endpoints?: Body tab → Form Data → add a field (key = field name), switch value to file type and pick a local file. Request auto-sets multipart/form-data. Note: some endpoints require a specific field name (file / image / upload) — check API docs.

Use cases

REST API debug: hand-craft requests for new endpoints
Third-party API: try OpenAI / WeChat / Alipay / Stripe endpoints
Production triage: reproduce error requests and inspect responses
Tutorials/docs: GIFs or screenshots showing API calls
Browser → tool migration: copy curl from DevTools, paste here

Use cases

REST API debug, third-party API trial, production reproduction, tutorials, curl migration. Backend, frontend, QA, support. Browser-native, CORS-aware, code snippet generation, env vars are the differentiators.