What it does
Send one HTTP request from the backend and inspect its status, headers, timing and body. Browser CORS restrictions do not apply to this server-side connection.
Send controlled API requests from the server.
Start with a sample or add your own input.
Your result will appear here.
Understand the format, the calculation, and what to look for.
Send one HTTP request from the backend and inspect its status, headers, timing and body. Browser CORS restrictions do not apply to this server-side connection.
Prepare requests with environment placeholders, query parameters, Bearer/Basic authentication and JSON/form/text/XML bodies. Build produces a redacted cURL export without sending a request. Query values, headers and bodies are masked; secrets in URL paths cannot be identified, so review exports before sharing.
Public internet destinations are supported. An administrator can optionally restrict origins. Rate limiting must be available before a request is sent. A fixed Tarsolution User-Agent identifies every call.
10 requests per minute per client IP, 30 per destination and 60 globally. JSON bodies up to 256 KiB, responses up to 1 MiB and a 12-second overall processing limit. Redirects are shown but never followed.
Headers and bodies are not saved. Credentials entered here are sent to the selected approved destination. Requests can change data there; review the URL and method before running.