API Documentation

A server-rendered /docs page documenting every collection's requests — a lightweight alternative to Postman's published documentation.

GET /docs renders a static, self-contained HTML page documenting every collection. It's built server-side straight from saved data/ state (not the browser's possibly-unsaved editor state), so there's no separate "publish" step and it's always current — just open it.

Click Docs in the topbar to open it in a new tab. For each collection you get a table of contents plus, per request: method, URL, description, params, headers, auth type, body, and any saved examples. Want a standalone file instead — to host on GitHub Pages, S3, or share directly — use Export ▾ → Documentation (HTML), which downloads the same page as volley-docs.html. To share the live page with someone outside your machine, point a tunnel (e.g. cloudflared tunnel --url http://localhost:5874) at your running Volley instance.

Credentials are redacted. The Authorization and Cookie header values, and every field on the Auth tab (tokens, passwords, client secrets, API keys), never appear — only the auth type is shown (e.g. "Bearer Token"). Everything else — including other header values, params, and the body — renders exactly as stored, same as Volley's other export formats. A hand-typed secret in some other header or in the body is not redacted; keep real secrets in {{environment variables}}, which are never part of a collection and so never appear in the generated docs.