Team Collaboration

Share requests, collections, and environments with your team through your own Git repository. There’s no separate sync service and no third-party cloud. Your API data lives alongside your code, works with any Git host, and follows the review process your team already uses.

Video guideTeam Collaboration walkthroughYouTube

How It Works

Save to your projectThunder Client saves collections to a thunder-tests folder in your Git repository.
Commit and pushShare changes through branches and pull requests, like any other code.
Teammates pullThe extension loads the latest collections automatically when the project opens.

Set Up Git Sync

Git Sync is configured in the Thunder Client settings in VS Code. Choose one of the two save locations below.

Open the Thunder Client settings

Open VS Code Settings and search for Thunder Client.

Choose where to save collections

Save to Workspace (Recommended)

Enable Save to Workspace to store collections in a thunder-tests folder at the root of your workspace. Thunder Client loads them automatically whenever you open the project in VS Code. To use a different folder, see the Workspace Relative Path tab.

Save to Workspace setting

Workspace Relative Path

Optional, and only used with Save to Workspace. By default, the thunder-tests folder is created at the workspace root. To save it somewhere else, set Workspace Relative Path to a path relative to the workspace.

Save in	Enter
A folder inside the workspace	`folder_name`
A nested folder	`folder_name/subfolder`
The parent of the workspace	`../`

Set Workspace Relative Path in the Workspace tab of VS Code Settings, not the User tab. A User-level value applies to every project you open.

Custom Location

Use Custom Location to keep collections in one fixed folder, shared across all your projects. Enter the folder’s full path.

Path type	Example
Absolute path	`/Users/name/api-collections`
Relative to your home folder	`$HOME/Documents/api-collections`

Custom Location setting

Notes

Existing requests are not moved automatically
To include requests created before you enabled Git Sync, create a thunder-tests folder and copy the collections and environments folders from the default storage location into it.
If both settings are enabled
Save to Workspace takes precedence over Custom Location.

Choose a Database Format

Thunder Client can store collections in Git in two formats. v3 is the default; switch to v4 if several people edit the same collections at once.

Database Format v3Default

One file per collectionEach collection is stored in a single JSON file.Best forSmall teams and individual developers. Database Format v3 file layout

Advantages

Easier to manage.
Faster to load.

Disadvantages

Merge conflicts can be hard to resolve when many people edit the same collection.

Database Format v4

One file per requestEach collection is stored as multiple JSON files.Best forLarger teams editing the same collections in parallel. Database Format v4 file layout

Advantages

Better suited to large teams editing together.
Easier to resolve merge conflicts.
Better for version control.

Disadvantages

Creates many files, which adds management overhead.
Deeply nested folders can cause long file path issues.

Switching Formats

Switch formats at any time from the VS Code command palette.

Action	Command
Upgrade to Format v4	`Thunder Client: Upgrade Database to v4`
Downgrade to Format v3	`Thunder Client: Downgrade Database to v3`