CookifyA better FastAPI /docs page, with no code changes
FastAPI gives you Swagger UI at /docs for free. Cookify keeps that page and adds what you need for working on it all day.
| Docs address | /docs |
|---|---|
| API document | /openapi.json, found from the page |
| Changes to your app | None |
Set it up
- Add Cookify from the Chrome Web Store.
- Run your app and open
http://localhost:8000/docs. - Save the API when Cookify asks, or choose Not now.
- Open an endpoint and send a request.
What you get on /docs
- Several endpoints open in tabs
- Request bodies that stay after a refresh
- Development, Staging and Production with a token for each
- Command palette on
Ctrl+P - Dark theme by default
Sign in with your OAuth2 route
If your app uses OAuth2PasswordBearer, sign in from the page with your username and password. The header shows who you are and when the token expires, and every request uses the token.
Questions
- Does Cookify work with FastAPI's /redoc page?
- No. Cookify works on Swagger UI pages, so use
/docs. - Do I need to change my FastAPI code?
- No. Cookify is a browser extension and reads the same document your docs page uses.
- Can I use it if I set a custom docs_url?
- Yes. Cookify detects Swagger UI on the page, whatever its address is.