Swagger Copy Kit

Swagger UI is great for exploring an API, but bad at getting requests and responses out of it. Swagger Copy Kit fixes that — on any Swagger UI instance, wherever it's hosted. WHAT IT DOES After you click "Execute" on an operation, a Copy button appears right next to it. Click it to copy the request and response as: • curl (bash) • curl (PowerShell 7 / curl.exe) • fetch() — a runnable JavaScript snippet • .http request block (VS Code REST Client / JetBrains HTTP Client) • Markdown bundle — request + response + status, ready to paste into Slack, Jira, or a GitHub issue • Raw capture JSON, or just the response body (raw or pretty-printed) A short history of your recent requests for the current tab is kept in the toolbar popup, so re-running a request never means losing the previous response. WORKS ANYWHERE Swagger UI is commonly self-hosted — localhost, an internal company network, any domain, any port, any path. Swagger Copy Kit detects Swagger UI automatically wherever you open it, including on embeds that don't expose Swagger's internal state (e.g. FastAPI's /docs). SECRETS STAY OUT OF YOUR CLIPBOARD Authorization headers, cookies, and anything that looks like an API key or token are masked by default in copied output (Bearer ••••), so you don't accidentally paste a live credential into a chat message or bug report. You can toggle this off per-copy when you do want the raw value. PRIVACY Everything stays on your device. There is no server, no analytics, no tracking, and nothing is ever sent anywhere — the extension simply has nowhere to send it. Captured requests live in per-tab session storage that clears when the tab or browser closes; your settings are stored locally. Full privacy policy: see the "Privacy practices" section of this listing. WHY THE "ON ALL SITES" PERMISSION Because Swagger UI can be hosted anywhere, the extension needs to be able to check any page you visit for Swagger UI's presence. On every other page it does nothing — no listeners, no reading, no network calls.