Your API. A request away.
Compose a request to a deployed Express API and inspect its response.
No Express destination is configured. Ask the operator to add an explicitly approved origin and exact API paths to destinations.json.
Request history
0This session only · latest 50| Time | Method | Destination | Status | Duration | Outcome |
|---|
Completed requests will appear here. No URLs, headers or bodies are retained in history.
Connection & security notes
The loopback backend forwards requests only to configured destinations. Redirects are never followed. DNS is checked and pinned; private, metadata and reserved addresses are blocked except the explicit local fixture.
Browser CORS does not apply to server-to-server forwarding. API authentication, TLS, firewall and IP allowlists still apply. Cancelling may not undo work already accepted by the target.
Timeout and rate limits vary by Express API. The 10 s timeout here is a local client limit. Reusing identifiers does not guarantee idempotency. Automatic retries are disabled.