REST Endpoint Visualizer

An OpenAPI document is the source of truth for a REST API, but as raw JSON it's almost impossible to read holistically — the paths object is a flat dictionary where each path maps to an object of HTTP methods, and the meaningful structure of the API (which resources exist, what you can do to each, what comes back) is buried under nesting. This visualizer lifts that structure out: it walks the document defensively, collects every operation, and groups them by resource so the API's shape becomes obvious in seconds rather than minutes of scrolling.

The colour-coded method badges and highlighted {params} are deliberate. Verbs carry meaning in REST — GET is safe, DELETE is destructive — and seeing a resource that exposes a red DELETE next to an amber PUT tells you instantly how mutable it is. Highlighting path parameters separates the fixed URL skeleton from the variable parts, which is exactly the distinction you need when wiring up a client. The parameter count folds in path-level parameters that every operation inherits and the request body, so the number reflects the real input surface rather than just what's declared on the operation line.

Because everything runs locally, you can paste specs you'd never upload to a third-party renderer, and the map rebuilds the instant your JSON becomes valid — so it doubles as a quick structural sanity check while you're authoring or editing a spec. The search box and method-filter chips keep even a several-hundred-endpoint document navigable: isolate every POST, or type part of a resource name, and the grouped map and counts update live.

When you want to go from this map to working calls, the OpenAPI Documentation Generator turns the same spec into polished reference docs, the JSON Schema Explorer drills into the request and response models behind each endpoint, and the API Request Builder helps you assemble and test an actual call against one of them.