Loading UtilityForge…
GUARDED SERVER EXECUTION / NO STORAGE
Send a narrowly bounded HTTPS request through a guarded server path. Every destination is resolved and validated before connection; redirects are checked again; and only a redacted, size-limited response is returned.
This tool does not permanently store arbitrary request secrets, and it redacts sensitive response fields before display. Environments and history are written to this device first, and a redacted history row also has an account copy on a plan that stores history; a credential-shaped variable keeps its value here even when the environment name is stored on your account. It cannot guarantee a third-party API’s handling of any credentials you choose to send.
{{VARIABLE}} in any field.No request has been run on this device in this browser. A row keeps the method, host, path, outcome, status, byte counts, and timing — never a header, body, query string, or response.
Request assembly
Request headers
1 / 20 header lines · Authorization-like names are redacted from the returned record.
Request body
Choose the right path
The guarded route has strict operational ceilings because it relays an outbound call. For a CORS-visible request sent directly by your own browser, use the separate builder instead.