Teams, roles and workspaces
Create a team and invite people by email; invitations are valid for seven days. Each member has a role:
- Admin: manages the team, members and workspaces
- Editor: creates and changes collections, environments, specs, mocks, monitors and flows
- Viewer: reads everything and can comment
Workspaces are personal, team or public. Public workspaces can be read by any signed-in Swastik Codes user, which suits sample collections for an open API. Everything syncs across your devices and your teammates' sessions, with optimistic concurrency so two people saving the same collection do not silently overwrite each other.
Live presence and comments
See who else is in a workspace or looking at the same request. Comment on any collection, folder or request, reply in threads, mention a colleague with @email (they get a notification and an email), and resolve threads when they are done. An activity feed lists what changed in the workspace and who changed it.
Version history
Every save of a collection records a version; the newest 50 snapshots are kept. Compare a version with the current state and restore it if needed, which creates a new version rather than erasing history. Deleted collections, environments, specs and flows go to the trash first and can be restored (kept for 30 days by default).
Forks, pull requests and reviews
For larger changes, fork a collection into your own workspace, work on it, and open a pull request back to the original:
- Fork the collection. The fork remembers its parent.
- Make your changes and open a pull request with a title, description and reviewers.
- Reviewers approve, request changes or comment. The diff shows what changed request by request.
- Merge with a three-way merge against the common ancestor. Conflicts are listed for you to resolve, choosing the source or target version of each.
Per collection, you can require merge checks: a number of approvals, at least one approval from an editor, and no outstanding change requests. Reviewers and authors are notified when a review is requested, submitted, merged or closed.
Webhooks and the public API
Workspace webhooks send signed HTTP POSTs on events such as collection.updated, pull_request.merged, monitor.run.failed or docs.published, with an HMAC-SHA256 signature for verification, retries with back-off and a delivery log. For scripts and CI, personal API keys (swc_…) work with the public /v1 API to list and update collections, environments, mocks, monitors, specs and flows.
curl -H "X-Api-Key: swc_your_key" \
"https://swastik.codes/api/v1/collections"Secrets stay out of shared copies
Current values of variables stay on your device and are stripped before anything is stored on the server, so a personal token is not shared with the team by accident. A secret scanner checks collections, environments and globals for things that look like keys and tokens, and highlights any that are exposed through a public workspace or published docs. See environments and variables.
Audit log and data retention
Workspace admins can open the audit log from the workspace settings: every save and delete, invitations and role changes, members removed, documentation published, versions restored and trash actions, each with who and when. Filter it, page back through it and download it as CSV. Admins also choose how many days to keep request history, monitor runs and the audit log; older data is deleted automatically. See Share a workspace with your team.
How it works
- Create a free account and create a team.
- Invite teammates and create a team workspace, or move an existing workspace into the team.
- Work together in the app: comment, fork, review and merge.
Frequently asked questions
Is collaboration free?
Yes. Swastik Codes is free to use today, including teams and shared workspaces.
What is the difference between a fork and a version?
A version is a snapshot of one collection over time. A fork is a separate copy you can change independently and later merge back through a pull request.
Can I export my workspace to Git?
Yes. Download the workspace as a ZIP with one JSON file per collection and environment, commit it to your repository, and import it back with a preview of the changes. Or let the swc CLI do it: swc workspace pull writes the files and swc workspace push saves your edits back, refusing to overwrite changes made in the app since.
Can people outside my team view a collection?
Put it in a public workspace, or publish it as documentation for a read-only reference.