API Tester
Test REST APIs, debug webhooks, import cURL commands, and share reproducible requests — all from your browser.
Ready to Test
Enter a URL and click Send to see the response here.
Built With Care
“When you test an API endpoint here, we route the request through our secure cloud proxy. This handles the common 'CORS' (Cross-Origin Resource Sharing) errors that usually block browser-based API tools, allowing you to test any public or local API effortlessly.”
REST API Tester & Debugger
Test your REST APIs directly from the browser with Axonix. Debug GET, POST, PUT, and DELETE requests, import cURL commands, set Bearer/Basic/API Key authentication, inspect headers, and share reproducible API calls with your team instantly.
- 1Select your HTTP method (GET, POST, PUT, DELETE, etc.).
- 2Enter the full URL of the API endpoint you want to test.
- 3Use the Auth tab to add Bearer tokens, Basic auth, or API keys.
- 4Add any necessary Headers or query Parameters.
- 5For POST/PUT requests, enter your JSON body payload in the Body tab.
- 6Click 'Send' to execute the request and view the status, time, and response data.
- 7Use the Body tab's form-data mode to build multipart payloads from key/value pairs and real file uploads.
- 8Re-run earlier calls from the request history panel, which keeps the last 50 requests in local browser storage.
- 9Watch the live Debug Console beneath the editor for transport route, timings, CORS fallbacks, warnings, and errors.
- 10If a CORS-restricted API fails, the tool automatically retries through the secure cloud proxy — or use the 'Force proxy' toggle to always route that way.
- Auth Presets: Bearer Token, Basic Auth, and API Key authentication with one-click setup.
- cURL Import: Paste any cURL command to auto-fill URL, method, headers, and body.
- Request History: Your recent API calls are saved locally for quick re-testing.
- CORS Handling: Browser requests run direct when possible, then automatically fall back to the secure cloud proxy (method allowlist, SSRF guard, timeouts, and size caps).
- Shareable Links: Encode your entire request configuration into a single URL.
- Response Analysis: View status codes, response time, payload size, and searchable JSON body.
- Pretty/Raw Toggle: Switch between formatted JSON tree view and raw response text.
- Form-Data Bodies: Key/value pairs plus real file uploads — sent by the browser or rebuilt through the proxy.
- Debug Console: A live panel logging every request — route, timings, warnings and errors — with filters, copy, and download.
- Cancellation: Any in-flight request can be aborted with the Cancel button, backed by client and proxy timeouts.
- Seven HTTP Methods: GET, POST, PUT, DELETE, PATCH, HEAD, and OPTIONS are available from the method selector.
REST API Tester & Debugger Specs
Limits
- HTTP methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
- Request size bounded by browser limits
Formats
- Input: URL, headers, JSON/form body
- Output: status, headers, body with JSON formatting
Defaults
- GET method
- JSON content type
How it works
- fetch with CORS proxy fallback
Honest caveats
- CORS-restricted endpoints require the proxy
- Cookies are not shared with the target origin
Real Ways People Use This
Debugging Webhooks
Simulate a webhook payload (POST request) to your local server or production endpoint to verify your listeners are working correctly.
Sharing Reproductions
Found a bug in your team's API? Configure the failing request and copy the 'Share' link to send a precise reproduction case to your backend developers.
Importing cURL Commands
Paste cURL commands from documentation, Stack Overflow, or browser DevTools to instantly populate the request without manually re-entering headers and body.
Quick Prototyping
Test public APIs (like weather, crypto, or social media) to understand their JSON structure before writing a single line of code.
Local Development Loop
Keep the tester open while writing endpoints: each call is stored in the local history (last 50), so you can re-run requests after every code change without rebuilding the URL.
Contract Checks Across Environments
Send the same request against staging and production and compare status codes, headers, and payload size to spot contract drift.
- Requests may run through a cloud proxy, so never send production secrets unless your team has explicitly approved that workflow.
- The proxy enforces hard limits: ~950 KB request bodies, ~800 KB responses (larger responses are truncated with a warning), and a 25s upstream timeout.
- Share links may include headers, body, and auth data — remove secrets before sharing publicly.
- Local development: run 'netlify dev' so the cloud proxy is served on :8888; CORS-restricted APIs that fail in the browser will also fail locally without it.
- 1Set correct method, URL, headers, and auth before sending the request.
- 2Inspect status code, response body, and timing for expected behavior.
- 3If sharing with teammates, remove secrets and reproduce with a sanitized request link.
- 4Open the Debug Console if a request behaves unexpectedly — it shows the transport route and any fallback or error details.