Reproduce requests
Combine method, URL, headers, and body in one screen to reproduce an issue and inspect the status code.
API Request Tester
브라우저 내부 처리
Send HTTP requests, inspect responses, and export them as cURL commands.
Safe API request testing
Reproducing an API response for documentation or a bug report means being able to write the request down exactly. Filling in method, headers and body and seeing both the response and the cURL form shortens that. Note that requests originate in the browser, so a server that does not permit CORS will block reading the response.
Share as cURL
Export a browser-built request as cURL so backend, QA, or operations teammates can reproduce it.
CORS still applies
Requests are sent from the browser, so the target API CORS policy can affect whether the request succeeds.
Errors you will hit
CORS errors
The request goes out from the browser, so you cannot read the response unless the target server allows CORS. It is a browser policy rather than a server fault — the same request succeeds from cURL in a terminal.
Before you paste anything sensitive
This tool sends a real request to the address you enter. Swap production tokens and personal data for test values, and mask headers before sharing results.
Things to check
Protect sensitive values
Replace production tokens, personal data, and internal API addresses with sample values before sharing.
Browser policy differs
A healthy server can still be blocked by CORS, auth-cookie rules, or mixed content policy. Browser results can differ from server-to-server calls.
CORS is the server's decision
A cross-origin request from a browser cannot be read unless that server sends permitting headers. This is the browser security model, not a tool limitation. APIs that do not allow it must be called from a terminal or your own server.
When you paste a token in a header
Values entered here stay in your browser, but they remain visible on screen and extensions can read them. Prefer a short-lived test token over a production access token.
GET and HEAD have no body
The spec technically allows a body on GET, but most servers and proxies ignore or reject it. Complex queries work better as query parameters or as a POST. If a response is empty, check this first.
More: step-by-step usage and worked examples
How to use it
- Enter the request method and URL.
- Add required headers and a JSON body when needed.
- Send the request and inspect status, headers, and response body.
- Mask tokens and personal data before copying cURL for sharing.
Real input and output
Turning a request into cURL
Input
GET https://api.example.com/users?limit=10
Authorization: Bearer <token>Output
curl 'https://api.example.com/users?limit=10' \
-H 'Authorization: Bearer <token>'A single cURL line is the most reliable way to hand a repro to a teammate.
Tools that pair well
- UUID Converter
- Base64 Encoder/Decoder
- JSON Formatter
- JWT Decoder
- URL Encoder/Decoder
- JSON YAML — Move structured data such as API responses, config files, and manifests between JSON, YAML, and simple CSV out