Guide: test HTTP endpoints in the browser
Before wiring an endpoint into your app, fire GET, POST, PUT, or DELETE with real headers and bodies. This tool builds the request and shows status, timing, and formatted response bodies — handy for contract checks, pagination, and error codes without opening Postman.
Calls originate from your browser: public APIs with CORS enabled work as expected; locked-down origins may fail due to server policy, not the tool itself. Tokens stay in your local session — avoid pasting production secrets on shared machines.
Use it to debug simulated webhooks, compare environments, or reproduce front-end bug reports. Once JSON looks right, feed it to JSON→TS or the JSON viewer to document the contract.
Step by step
- Set method and URL — Pick GET for reads or POST/PUT/PATCH with a JSON body. Add query params in the URL or dedicated panel when available.
- Configure headers and auth — Add `Content-Type`, `Authorization: Bearer …`, or custom headers the API requires. Some servers need a specific `Accept` value.
- Send and inspect the response — Review HTTP status, response headers, and body. 4xx/5xx payloads help you fix validation or error messaging.
- Iterate and document — Tweak body or headers and resend. Copy sample responses into automated tests or the JSON→TypeScript tool.