How to use API Request Tester
- Enter the HTTPS destination, method, headers and optional request body.
- Review exactly what the destination will receive, tick the confirmation and select Send API request.
- Inspect the HTTP response or CORS/network error; download current response JSON if needed.
Example: API Request Tester
Review and send a browser-direct HTTPS API request.
Supported inputs and limits
- Requests go directly from your browser to the entered HTTPS destination.
- That service receives the body and any entered API key; this site does not receive them.
- Review and confirmation are required before Send.
- Supports GET, HEAD, POST, PUT, PATCH and DELETE; no GET/HEAD body.
- Only valid UTF-8 response text is supported; malformed/binary text is refused without replacement.
More details
Request body and response stream are each limited to 1 MiB, with at most 20 safe headers/16 KiB total and a 15 second deadline.
Cookies are omitted, redirects refused, referrer omitted and request caching disabled.
No retries, server proxy, stored tokens or history.
URL credentials, app-origin, local/private-name/IP-literal endpoints and nonstandard ports are refused.
Hostname syntax checks do not prove DNS/public routing; browser DNS, TLS and CORS rules remain in force.
Where your input is processed
Your reviewed request goes directly from this browser to the entered HTTPS service. That service receives the body and any entered API key; this site does not receive them. No request/token history is saved.
Questions about API Request Tester
Why can an API work elsewhere but fail here?
The browser enforces CORS, TLS and request-header restrictions. This tester refuses redirects and has no server proxy to bypass those checks.
Where does an entered Authorization header go?
It is sent directly from the browser to your reviewed HTTPS destination for that request. The site does not receive it, and the tester does not save tokens or history.
Do hostname checks guarantee public DNS routing?
No. The form rejects obvious local names, IP literals and unsupported addresses, but syntax checks cannot prove how a hostname resolves in your browser.