Learn
Learn Swastik Codes, one step at a time
20 short lessons, in order. Each one does one job from start to finish with exact steps and commands, so you can follow along in the app as you read. New to API tools? Start with lesson 1.
Get started
Send a request, keep it in a collection and switch between environments.
Send your first request
Open the app, send a request, read what came back and keep the request for later.
Environments and variables
Write {{baseUrl}} once, switch servers with one click and keep secrets on your device.
Collections, folders and authorization
Group requests into folders, set authorization once, and keep a fresh login token automatically.
Find and test an API from the marketplace
Search the marketplace, pick an API you can trust, fork it into your workspace and send a request with your own key.
Test your API
Write tests, run whole collections, and find what is flaky, untested, insecure or open to the wrong users.
Write your first tests
Turn "it looks right" into checks that run on every send: status, fields, speed and shape.
Run a whole collection
Send every request in order, feed it test data, read the report and take the same run to CI.
Compare responses and environments
See what changed between two responses, and check staging against production request by request.
Find flaky tests and check coverage
Catch the tests that fail now and then, and find the endpoints and error cases nobody tests.
Check who can do what
Send requests as different users, and check every role against every endpoint in one run.
Security checks and invalid input
Find endpoints that work without signing in, risky CORS and headers, and inputs that crash the server.
Automate
Run tests in CI, catch breaking changes, keep the workspace in Git, mock and monitor.
Run your tests in CI with swc
Install the swc tool, run collections in any pipeline, and fail the build when a test fails.
Catch breaking changes before they ship
Let swc read the API from your code, compare it with the main branch and stop breaking changes in review.
Keep your workspace in Git
Store collections as files next to your code, review them in pull requests and sync both ways without overwriting anyone.
Mock servers
Answer requests from saved examples, so front ends and tests can work before the real API is ready.
Monitors, alerts and the reliability report
Run your tests on a schedule, get told when they fail, and see how reliable the API has been.
Use your collection from an AI coding assistant
Give an AI coding assistant safe access to your requests, so it can check the real API while it codes.
Work as a team
Share workspaces, publish documentation and APIs, and move over from Postman.
Share a workspace with your team
Invite people with the right role, see who changed what, and decide how long data is kept.
Publish and export API documentation
Turn a collection into documentation others can read, online with a link or as a single HTML file.
Publish your API on the marketplace
Register your organization (or create a personal profile), choose Publish to marketplace on a collection, and track how developers use it.
Move from Postman
Bring collections, environments and scripts across, see what needs attention, and switch your CI from Newman to swc.