AIZENAPI Request ClientABACUS Express
Local workspace
REQUEST WORKSPACE

Your API. A request away.

Compose a request to a deployed Express API and inspect its response.

An explicit destination. A controlled request.Only allowlisted URLs can be reached. Credentials stay in this tab. No automatic retries.
Bot protection / 봇 검증Checking relay configuration…

Request

Express defaults

Headers

EnabledKeyValue

Enable x-org-id and x-api-key after entering your issued values. Content-Type is prefilled.

Local limits: 64 KiB body / 10 s timeoutMemory only

Response

Ready

Ready when you are.

Send a request to see the status, timing, headers and response body here.

HTTPJSONTEXT

Request history

0This session only · latest 50
TimeMethodDestinationStatusDurationOutcome

Completed requests will appear here. No URLs, headers or bodies are retained in history.

History retains only destination label, method, status and timing. Keys, tokens, cookies, URL paths, queries and bodies are never copied into 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.