Docs generated from the request you actually sent.
Every request can generate its own Markdown documentation — headers, parameters, and a response schema table pulled from the real response, not hand-typed. Edit it, and HTTP Titan tells you when it drifts from the request again.
Documentation that doesn't start from a blank page.
Three things generated docs replace.
A real template, not a blank editor
One click builds a Markdown page from the request itself: a headers table, a query parameter table, the request body, and — from the actual JSON response — a response schema table with a working curl example underneath.
Know when docs go stale
Change a request after its docs were written, and a side-by-side diff shows exactly what changed — your saved documentation on one side, a freshly regenerated template on the other. Apply it or keep editing by hand.
One page for the whole collection
A collection overview plus every folder and request underneath it exports as a single HTML page — something to actually hand a teammate or a partner, not a pile of separate screenshots.
API Documentation, answered.
The practical questions before you generate your first doc page.
Does the response schema table require me to define a schema first?
No — it's inferred directly from the actual JSON response body the request most recently received: field names, types, and one level of nested objects flattened as parent.child rows.
What happens if I edit the generated docs and then change the request?
Nothing overwrites your edits automatically. You'll see a prompt that the docs may be out of date, with a side-by-side diff between what you saved and a freshly regenerated template — you choose whether to replace it or keep your version.
Can I document a collection, or only individual requests?
Both — a collection (and each folder inside it) has its own Markdown documentation field, separate from any individual request, and the collection-level doc becomes the introduction page when the whole thing exports.
What does exporting actually produce?
A single self-contained HTML file assembling the collection overview, every folder, and every request's documentation in order — something you can send or host, not a live app that requires a login.
Talk to us.
Tell us about your team and what you're building. We'll get back to you.