Case summary
Case file · REST APIs
Every API leaves clues.
Point it at an OpenAPI spec, a documentation page, or a live endpoint. It finds the endpoints, explains what they do, and lets you test them right here.
Try a case:
01 Discover
Five tiers, stopping at the first that works:
- Direct spec — the URL is an OpenAPI/Swagger document
- Linked spec — found in the page or its Swagger UI / Redoc config
- Well-known paths —
/openapi.json,/v3/api-docs, … - Docs scraping —
GET /users/{id}, curl & fetch examples - Live probing — JSON roots and their hypermedia links
02 Understand
Every endpoint gets a plain-language summary, the inputs that matter, what comes back, and practical tips: pagination, auth, idempotency, enum values, deprecations.
03 Test & export
Requests are generated from the schemas. Send them, compare the response with the documented schema, copy as curl, and export everything to Markdown or JSON.