1. What does this tool do
This free online API tester sends HTTP requests (GET, POST, PUT, PATCH, DELETE) to any URL from your browser. Use it to test API, send HTTP request, or debug REST API with headers and body. Add headers and a request body, then see the response status, headers, and body. No server proxy—requests go directly from your machine. Free and useful for debugging APIs and checking endpoints. Ideal for debug APIs, check auth, documentation examples, or quick checks.
2. How to use it
Quick start: Enter the full URL, select method (GET, POST, etc.), add headers (e.g. Authorization, Content-Type) and body if needed, click Send, then view status code, response headers, and body.
- Enter URL — Type the full endpoint URL (e.g. https://api.example.com/v1/users).
- Select method — Choose GET, POST, PUT, PATCH, or DELETE.
- Add headers — Set Content-Type, Authorization, or other headers as required by the API.
- Add body — For POST/PUT/PATCH, enter JSON or other body content.
- Send — Click Send and view status code, response headers, and body. Use for debugging or exploration.
3. How it works
The tool uses the browser’s fetch() (or similar) to send the request to the URL you provide. Because the request originates from your browser, the same-origin policy and CORS apply: the target server must allow your origin to read the response. No data is sent to the tool’s server; it only runs in your browser. Requests go directly to the target API.
4. Use cases & examples
- Debug APIs — Test endpoints during development; verify status and response shape.
- Check auth — Send a request with a Bearer token or API key and confirm 200 vs 401.
- Documentation — Try examples from API docs and see real responses.
- Quick checks — GET a URL to see if it returns JSON or HTML.
Example
- GET https://api.example.com/health → 200, body “ok”.
- POST with JSON body and Authorization header → 201 or error with message.
5. Limitations & known constraints
- CORS — If the API does not allow your origin, the browser will block the response. Use a CORS-enabled environment or a proxy for local testing.
- No cookies to other domains — Cookies are sent per browser rules; cross-domain cookies may not be sent.
- Browser only — No command-line or server-side use; no built-in scripting or environment variables.