ProductFree to use, no paid plans
The whole API platform, from first request to production
Swastik Codes is one place to design, send, test, mock, document, monitor and share APIs, for REST, GraphQL, gRPC, WebSocket, Socket.IO, SSE, MQTT and MCP. Use it in the browser, on your desktop, from the terminal, in VS Code, or inside your own server.
Get started freeSign inOpen the appRead the complete guide
- 8protocols
- 26features
- 5ways to use it
- 0paid plans

One account, five places
Five ways to use Swastik Codes
The same collections, environments and tests everywhere. Start in the browser and add the others when you need them.
Web app
Runs in your browser, nothing to install.
- All eight protocols in one app
- A free account (GitHub or email) to send
- Reaches localhost through swc bridge
Desktop app
Windows, macOS and Linux; reaches localhost.
- Requests run on your computer: localhost, LAN and VPN hosts
- Windows, macOS (Apple silicon and Intel) and Linux
- Works without an account; sign in to sync
Command line (swc)
Scan code, run tests in CI, mock locally.
- swc init turns your routes into a collection
- swc run in CI, with JUnit and HTML reports
- swc mock, swc compare, swc security and more
VS Code extension
Requests and tests next to your code.
- Collections and environments in the sidebar
- Collections run in the Test Explorer
- Project Sync keeps a collection in step with your code
Docs for your server
pip and npm: docs served by your own app.
- FastAPI, Flask, Django, Express, NestJS, Fastify
- Documentation plus a request collection
- 22 KB for the browser, no dependencies
New · pip and npm
Docs for your server: like FastAPI's /docs, for any framework
Install swastik-codes or @swastik-codes/docs, add one line, and your own API serves full documentation at /swc/docs and a request collection at /swc/collection, both built from the OpenAPI document it already has.
pip install swastik-codes
from swastik_codes import mount
mount(app)npm install @swastik-codes/docs
app.use(swastikCodes({ spec }))- Documentation with code samples in cURL, JavaScript, Python, Go and PHP
- A collection page: params, auth, headers, JSON, form and file bodies, then Send
- Edit the title, introduction, servers, sections and names in one
swastik-codes.json - 22 KB for the browser (Swagger UI is about 427 KB) and no dependencies on your server

Design to production
The whole API lifecycle in one place
Each stage uses what the last one made: the definition becomes a collection, the collection gets tests, the tests become monitors, and the same requests become mocks and documentation.
-
Design
Write or import an OpenAPI, Swagger or AsyncAPI definition, lint it, tag versions and generate a collection that stays in sync with it.
-
Send and debug
Build requests for any protocol with params, headers, every body type and 12 auth schemes, read the response with a timing breakdown, and turn it into code.
-
Organise
Keep requests in collections and folders, switch between environments, and keep tokens in current values or an encrypted vault.
-
Test
Write pre-request and test scripts with swc.* (Postman scripts run as they are), run whole collections with data files, and find flaky, untested or insecure endpoints.
-
Automate
Build a collection from your code, keep it in sync on every push, run it in CI, and chain requests into flows triggered by webhooks.
-
Mock
Turn saved examples into a hosted mock API with request matching, delays and templates, or run the same mock on your computer.
-
Document
Publish a collection as searchable documentation with code samples, or let your FastAPI, Express or NestJS app serve its own docs.
-
Load and monitor
Push saved requests with virtual users and live percentiles, then schedule the collection and get alerts by email, Slack, Teams or webhook.
-
Share
Work in team workspaces with roles, comments, version history, forks and pull requests, and publish APIs on the marketplace.
26 features
Every feature
Each one has its own page with how it works, examples and answers to common questions.
Protocols
One client for request/response and streaming APIs.
REST API client
Send any HTTP request from the browser with params, headers, every body mode, auth helpers, a timing breakdown and saved examples.
GraphQL client
Introspect a schema, explore types, write queries with autocomplete, run subscriptions over WebSocket and test the results.
WebSocket client
Connect to wss:// endpoints, send text or binary frames, keep saved messages and search a timestamped message log.
Socket.IO client
Connect to Socket.IO v2, v3 or v4 servers, emit events with arguments, wait for acks and listen to the events you care about.
SSE client
Subscribe to text/event-stream endpoints with headers and auth, filter event types, resume from Last-Event-ID and stream POST responses.
gRPC client
Load services from .proto files or server reflection, make unary and streaming calls with metadata and deadlines, and test the results.
MQTT client
Publish and subscribe on MQTT 3.1.1 and 5 brokers over mqtt://, mqtts://, ws:// or wss://, with QoS, retain, last will and MQTT 5 properties.
MCP client
Connect to remote MCP servers, list and call tools, read resources, get prompts, answer elicitation and sampling, and debug OAuth discovery.
Testing and reliability
Scripts, runs, load and scheduled checks.
API testing
Pre-request and test scripts with the swc.* API, chai assertions, JSON schema validation, swc.sendRequest and familiar libraries.
Collection runner
Run collections or folders with iterations, CSV/JSON data files, delays and bail rules, then export JSON, JUnit XML or HTML reports.
Load testing
Run saved requests with virtual users and fixed, ramp-up, spike or peak profiles, and watch throughput, errors and latency percentiles live.
API monitoring
Schedule collection runs with cron, retry flaky checks, and get email, Slack, Teams or webhook alerts on failures and recoveries.
Design, mock and document
Everything around the API itself.
Mock servers
Turn saved examples into a hosted mock API with request matching, response headers to pick examples, delays, templates and a call log.
API documentation
Publish a collection as a searchable docs site with code samples, examples, custom Markdown pages and credentials masked automatically.
API design
Edit OpenAPI, Swagger and AsyncAPI definitions, lint them, tag versions, and generate collections and contract tests that stay in sync.
Flows
Chain saved requests on a canvas with conditions, loops, delays and expressions, then run the flow by hand or from a webhook.
Code generation
Turn any request into a snippet for cURL, JavaScript, Python, Go, Java, C#, PHP, Ruby, Swift, Kotlin, Rust and more.
API catalog
Search your team's APIs by name, owner, tag or endpoint, with their status, docs, mocks and monitors.
Workflow and teams
Work the way your team already does.
Collaboration
Team workspaces with roles, realtime presence, comments and mentions, version history, forks, pull requests, reviews and webhooks.
Import and export
Import Postman, Insomnia, OpenAPI, Swagger, cURL, HAR, RAML, WSDL and GraphQL schemas; export to Postman v2.1/v2.0/v3 or OpenAPI 3.
Environments and variables
Environments for every stage, layered variable scopes, dynamic values, an encrypted local vault with external providers, and a secret scanner.
Authorization
12 auth schemes including OAuth 2.0 with PKCE and auto-refresh, JWT signing, AWS Signature v4, Digest, NTLM and Hawk, inherited from folders.
VS Code extension
Your collections and environments in the editor. Send requests, run collections as tests and keep a collection in sync with your code.
Command-line tool (swc)
Scan a project's code for its API routes and save them in a collection, keep it in sync as the code changes, and run collections in CI.
Docs for your server
One line in FastAPI, Express, NestJS, Flask or Django serves documentation and a request collection built from your OpenAPI spec.
GitHub sync
Pick a repository and a branch; the API routes in the code become a collection you can test, updated on every push.
Compare the five
Which one should I use?
Most people use two or three: the web app every day, the desktop app or swc bridge for local APIs, and the CLI in CI.
| Capability | Web app | Desktop app | Command line | VS Code extension | Docs for your server |
|---|---|---|---|---|---|
| Install | Nothing | Installer | One command or npm | From the Marketplace | pip or npm package |
| Account | Free account to send | Optional, to sync | Optional, for workspaces | Optional, adds your collections | Not needed |
| Reaches localhost | With swc bridge | Yes | Yes | Yes | Its own server |
| Runs collections | Collection runner | Collection runner | swc run | Test Explorer | No |
| Best for | Everyday work and teams | Local and private APIs | CI and automation | Working next to your code | Your API's readers |
Five minutes
Get started in three steps
- Create a free accountSign up with GitHub or email at swastik.codes/signup. No credit card.
- Bring your requestsImport Postman, OpenAPI, Insomnia, HAR or a cURL command, or connect a GitHub repository.
- Send, test and shareSend a request, add a test, run the collection and invite your team.
Frequently asked questions
What is Swastik Codes?
Swastik Codes (SWC) is an API platform: an API client for REST, GraphQL, gRPC, WebSocket, Socket.IO, SSE, MQTT and MCP, with tests, a collection runner, load tests, mock servers, monitors, API design, published documentation and team collaboration. It runs in the browser, as a desktop app, as the swc command line, in VS Code, and as docs packages your own server can serve.
Is it free?
Yes. Swastik Codes is free to use today, including teams and shared workspaces, and there are no paid plans. The web app needs a free account (GitHub or email) to send requests; the desktop app, the CLI and the docs packages also work without one.
Which one should I start with?
Start with the web app: nothing to install, and everything you save syncs to the desktop app and VS Code later. Add the desktop app or swc bridge when you need localhost or a private network, the swc CLI for CI, and the pip or npm docs package when your own API should serve documentation.
Can my own API serve Swastik Codes documentation?
Yes. pip install swastik-codes (FastAPI, Flask, Django) or npm install @swastik-codes/docs (Express, NestJS, Fastify, Hono, Koa), then add one line. Your server then shows documentation at /swc/docs and a request collection at /swc/collection, built from its OpenAPI document, and a swastik-codes.json file edits the text without code changes.
Can I move from Postman?
Yes. Import Postman collections (v2.0, v2.1 and v3), environments, globals and data dumps. Scripts written against the pm.* API run unchanged, because pm and swc are the same object in the sandbox.
Where is my data kept?
Local workspaces stay in your browser or on your computer. Cloud workspaces sync through your account so teammates and your other devices see them. Current values of variables never leave your device, and secrets can live in an encrypted vault.
Free to start · no install
Start with the request you are debugging today
Create a free account, then import a collection, paste a cURL command or point it at a GraphQL endpoint.
- Learn step by stepShort lessons for every feature.
- See what is newThe changelog, newest first.
- Ask us anythingThrough the contact page.