Your API workspace belongs in git
Your code, your infra, your configs are all in version control. Your API workspace never was — until now. Commit it, branch it, review the diff, and merge without losing anyone’s work.
Create workspace
Your code is versioned. Your infra is versioned. Your configs are versioned. Your API workspace wasn’t.
A teammate changes an endpoint and you find out when a test breaks. No diff, no review, no history. Git Sync closes that gap — your requests, environments, folders, and runners live as plain files in a repository you own.
The workflow you already know
Point it at a repo you already have, or let RESTK start a new one. It does the git work from inside the app — no separate client — and they’re ordinary files in an ordinary repo, so your terminal and editor work too.
Commit & branch
Commit an endpoint change alongside the code change that motivated it. Branch without touching anyone else’s work.
Review the diff
See a readable diff of exactly what changed — review an API change the same way you review code.
Merge, keep everything
A real field-level merge. Renames stay renames, not delete-and-re-add. Moves keep the request intact.
Full history
Every change is in your repo — see who changed what, and when.
Two people.
One request.
No lost work.
Plain git drops raw conflict markers into a file, and many tools just overwrite one side. RESTK does a real field-level merge — non-conflicting edits both survive, and when you genuinely edit the same thing, both versions come up side by side so you resolve by choosing.
- ✓Different fields never conflict — your URL change and their header change both survive.
- ✓Same-field conflicts open a side-by-side resolver, with a manual edit if you want finer control.
- ✓Renames stay renames. Moving a request between folders keeps it intact.
“But won’t that commit my secrets?”
No — by design. Mark any value as a secret and it stays out of every commit. Teammates see that the workspace expects that secret, so they know what to fill in — but never your token or key.
- ✓Marked secrets are never committed and never synced — in any mode.
- ✓A secret scan runs before every commit and push.
Git is one of three
You choose where each workspace’s data lives — and mark any value as a secret to keep it out of all of them.
Nothing leaves your machine
No account, no network, fully offline. No infrastructure of ours in the loop.
Plain files in a repo you own
Commit, branch, and merge — with a visual conflict resolver. Secrets are never committed.
Real-time sync for teams
Instant sync across devices, encrypted on your device before it leaves.
The whole workflow, end to end
Four short videos: set it up, run every git operation, and resolve a conflict — from an empty workspace to a clean merge.
The quick tour — why your API workspace belongs in git, and what that unlocks.
Questions, answered
Does putting my API workspace in git commit my secrets?
No. Any value you mark as a secret is kept out of every commit — teammates see which secrets a workspace expects, so they know what to fill in, but never your actual values. A secret scan also runs before every commit and push and stops a sensitive value before it enters your history.
Does Git Sync work with GitHub, GitLab, or my own git server?
Yes. Your workspace is stored as ordinary files in a standard git repository you own, so it works with any git host — GitHub, GitLab, Bitbucket, or a self-hosted server. You can point RESTK at a repository you already have, or let it start a new one.
Do I need an account to use Git Sync?
Yes — Git Sync signs in with a RESTK account. If you want to work with no account at all, use a local workspace: it needs no account and no network. Git Sync and real-time Cloud sync both use your RESTK account.
Does it work offline?
Yes. Git mode is offline-first: you can commit locally with no connection and push when you are back online. Everything keeps working whether or not a remote is reachable.
Can I still use my own git client or the terminal?
Yes. RESTK handles staging, committing, branching, pushing, and pulling from inside the app, but because the workspace is ordinary files in an ordinary repo, your usual git tools, terminal, and editor work alongside it.
Put your API workspace in git
Native on Windows — and macOS. Local workspaces are free with no account; Git Sync signs in with your RESTK account.
Your workspace, versioned in a repo you own — secrets never committed.