Testing APIs

katu http (or alt r inside a session) opens a small request tool in the brand palette: cycle the method, type a URL, add headers, edit the body in $EDITOR, and send. Status, timing, size, and a pretty-printed JSON body (server field order preserved) come back in a scrollable viewer that treats a 500 as a result to inspect, not an error.

{{base_url}}-style variables resolve at send time against switchable environments (e), defined globally in ~/.katu/http/environments.toml or per project in a committable .katu/http.toml. Tokens live only in your environment files — the UI and every file on disk keep the raw templates.

Every send lands in a filterable history (h), and S saves the request to a hand-editable TOML collection (c to browse). As a popup, hiding it with alt r keeps the drafted request alive; katu http --window gives it a full window.