Thunder Client Support Save

Thunder Client is a lightweight Rest API Client Extension for VS Code.

Project README

Thunder Client

installs version

Thunder Client is a lightweight Rest API Client Extension for Visual Studio Code, hand-crafted by Ranga Vadhineni with a simple and clean design. The source code is not open source. You can report any Bugs Or Feature requests here.

Story behind Thunder Client

  • Read Launch Blog Post on Medium


  • 1 Million downloads on July 13, 2022
  • 500K downloads on Dec 20, 2021
  • Extension launched on Mar 31, 2021

How to Use

  • Install the extension, click the Thunder Client icon on the Action Bar.
  • From the sidebar click New Request button to test API
  • Video:
  • Minimum VS Code version now required is v1.66.0


  • Thunder Client is built with Javascript, Typescript, Flexbox, Ace Editor, Got, Nedb.

Main Features

  • Lightweight Rest API Client for VS Code
  • Simple & Easy to use UI
  • Supports Collections and Environment variables.
  • Scriptless Testing: Test API response easily with GUI based interface .
  • Themes: The extension supports VS Code themes.
  • Offline & Local Storage: Works offline and saves all the requests data locally on your device.

Git Sync

This feature is useful to share requests with your team by saving data in a git project.

Integration with Git is supported by VS Code settings below, choose any one as required. To view Thunder Client settings, open the VS Code settings UI and search for Thunder Client to view all of the extension's settings.

  1. Save To Workspace (Recommended): Enable this setting when you'd like to save requests data in the current workspace. This will create a thunder-tests folder in the root of the workspace. The extension will load the data automatically when you open the project in VS Code.
    • Workspace Relative Path (Optional): The default location of the thunder-tests folder is at the root of your workspace. Use the Workspace Relative Path setting to specify a different relative path (see below for examples).
    • Make sure the Workspace Relative Path setting is "Workspace", not "User".
    • Example 1: To save in the Child folder of the workspace, the relative path is FolderName or Child/FolderName
    • Example 2: To save in the Parent folder of the workspace, the relative path is ../
  2. Custom Location: Use this setting when you'd like save all of the requests data in one fixed location. Enter the full folder path to save the data.
    • Supports relative path to user root directory. Use prefix $HOME. e.g $HOME/Documents/folderName

  • WARNING: The Environment file which stores the secrets is also saved in the same git folder (see Note 1 below).
  • Note 1: The environments will be stored in thunderEnvironment.json, in the thunder-tests folder. If you'd like to exclude any secrets from thunderEnvironment.json file then use Local Environment to store values locally on your computer.
  • Note 2: File changes are not detected by the extension (yet), if you pulled changes from git, click the Reload icon in sidebar.
  • Note 3: Please restart VS Code after updating settings.

Location of the request files

The files and requests data location paths:

  • Windows: %APPDATA%\Code\User\globalStorage\rangav.vscode-thunder-client
  • Mac: /Users/{{userName}}/Library/Application Support/Code/User/globalStorage/rangav.vscode-thunder-client/
    • Replace {{username}} with yours.

Code Snippet

Code snippet generation is available for the following languages:

  • C# - HttpClient
  • cURL
  • Dart Http
  • JavaScript Fetch & Axios
  • Php Laravel
  • PowerShell
  • Python requests & http.client
  • and other languages are powered by httpsnippet

Open request view and click the {} icon to see the Code Tab:

Key Features

  • Supports most languages including Flutter, Dart, PHP Laravel, C#, JS, Python, Swift, etc.
  • Updates the code snippet in real-time as you make changes to a request.
  • You can save the code snippet to a file or open the snippet on VS Code tab using Screenshot 2022-08-01 at 17 09 12

Scriptless Testing

  • We need to write a lot of boilerplate code in Postman and other clients to do basic testing using scripting (like status code equals 200). So I implemented GUI-based tests, where you can select a couple of dropdowns to do most standard tests easily, without any scripting knowledge.
  • Tests can be done for strings, numbers, count, and type checking.
  • Json schema validation.
  • Setting env variables is also possible in the Tests section.
  • Re-arrange tests order using drag & drop.
  • Use Json Query Tests for Xml Response. (Xml is converted to Json for tests).

Environment Variables


The following environments can be used in Thunder Client, ranked from least to highest precedence:

  1. OS Environment Variables: You can use OS System environment variables as global variables using the format {{variable}}.

  2. Local Environment: You can use Local Environment to save secrets and transient tokens locally on your computer; useful to exclude secrets from a git project. This environment is a global type and the variables are available to all collections. The values will not be saved in the main thunderEnvironement.json file (See above image, option 3)

  3. Global Environment: You can use Global Environment to save variables and share them with all collections. The values will be stored in the main thunderEnvironment.json file. (See above image, option 2)

  4. env file: You can use .env files in Thunder Client. To use a .env file follow the below steps:

    • Create an Environment (using option 1 in above image).
    • Open the Environment view, where you will see the option Link to .env file.
    • Select the .env file and save it. Now you can use the variables in Requests using {{variable}}.
    • The variables in the .env file should be in the format:
  5. Active Environment: To use an environment's variables, you need to make it active using the options menu ..., then select Set Active.

  6. Attach Env to Collection (Optional): You can attach an environment to a collection from the Collection Settings view. Use this option when you'd like to link multiple collections to multiple environments. The values in this environment will take precedence over the active environment. If you change environments frequently, this option is not recommended. Please see the example below:

    CollectionA -> EnvA
    CollectionB -> EnvB
    CollectionC -> EnvC

How to use Environment Variables

  • To use environment variables use the format {{variableName}}. You can use variables in Query Params, Headers, Body & Tests.

Import .env Files

  • You can import Thunder Client, Postman and .env files using the Import Menu Option (see above image, option 4). More details here.

Set Environment Variable

Setting environment variables is supported in the Tests tab. Follow the steps below:

  • Create an environment first from the Env tab (if it's not already created).
  • In the Tests tab, select the Set Env Variable dropdown option (The action will automatically become setTo).
  • Enter the appropriate source of the variable value in the left input box:
    • Header: Enter header.headerName where headerName is the response header name.
    • Cookie: Enter cookie.cookieName where cookieName is the response cookie name.
    • JSON Response: Enter json.propertyName where propertyName is the JSON key in the response body.
    • Text Response: Enter the text keyword. This sets the entire response body to the variable.
    • Custom Value: To set any custom value manually, Just type the text as required in the left input e.g processing
    • Clear Value: To clear values use null keyword in the left input.
    • Delete Variable: To delete a variable completely use delete keyword in left input.
  • In the value input, enter a variable name in the format {{variableName}}.
    • When it matches a variable name in Env, it will turn green. If the variable doesn't exist, it will be created.
  • Now execute the request. You will see the variable value set in the Env tab.
    • If you don't see the change in the Env tab, close and re-open the tab to refresh it.

Set Env with Scope

The default location will be Active Environment when you use {{variable}}. You can use a scope to control which environment variable to set the value explicitly.

  • To set a variable in the local environment use {{variable, local}}.
  • To set a variable in the global environment use {{variable, global}}.
  • (optional) To set a variable in the active environment use {{variable, active}}. Use this format only when you have attached an Environment to a Collection, otherwise use the {{variable}} format.


  • OAuth 2.0's callback url, when grant type is Authorization Code, needs to be entered into your oauth server trusted redirect url list.

  • OAuth authentication credentials are sent via header or body; please select the appropriate one based on your server requirements.

  • Manual SSL Certificates

    • Provide SSL certificate paths for auth, using the relative path to the workspace or absolute paths.
    • Use the Certificates VS Code setting, see example below:
    "thunder-client.certificates": [
                "host": "",
                "certPath": "ssl/cert.pem",
                "keyPath": "ssl/keyfile.key",
                "pfxPath": "ssl/pfx.p12",
                "passphrase": "test"
                "host": "localhost:8081",
                "pfxPath": "/Users/test/Documents/ssl/pfx.p12",
                "passphrase": "test"
                "host": "",
                "certPath": "ssl/cert.pem",
                "keyPath": "ssl/keyfile.key"


  • You can create or modify cookies using the Cookie header in the request.
  • To clear existing cookies for the request, use Clear All button in the Cookies Tab:


Path Variables

Path variables are supported using the format {variable} in the url field:

  • Example 1:{customerId}
  • Example 2:{customerId}{name}/

System Variables

System variables are useful to generate random/dynamic data for use in request query params or body. The format is {{#variableName}}

  • {{#guid}} — Generates random uuid.
  • {{#string}} — Generates random string.
  • {{#number}} — Generates random number between 1 to 1000000.
    • Custom Range: use {{#number, min, max}}
      • example: {{#number, 100, 999}}
  • {{#email}} — Generates random email.
  • {{#date}} — Generates unix date timestamp in milliseconds.
    • Custom date format: use {{#date, 'YYYY-MM-DD hh:mm:ss:fff'}}, the format should be in single quotes.
    • Unix timestamp: use {{#date, 'X'}}, this will output unix timestamp in seconds.
  • {{#dateISO}} — Generates date ISO format.
  • {{#bool}} — Generates true or false.
  • {{#enum, val1, val2, val3,...}} — Generates one of the enum values provided (comma separated).
    • example: {{#enum, red, green, blue}}
    • example: {{#enum, 1, 2, 3}}


  • Proxies are supported using the VS Code proxy setting, in the format: http://username:[email protected]:port.
  • exclude Proxy Host List: Use this setting to exclude hosts from proxy, supports comma separated values e.g:,


  • To send a request using the HTTP/2 protocol, please select HTTP/2 option in VS Code settings for Http Version.


  • The following imports of Collections and Environments are supported:
    • Postman 2.1.0 format
    • Insomnia v4 json file
    • Open API v3 json or yaml files
    • Thunder Client
  • You can import or export Thunder Client Collections and Environments data.
  • Import Curl is now supported from Activity tab.
    • Keyboard shortcut Cmd/Ctrl + u
  • Import of .env files is also supported, select Import from Env tab and choose .env file

How to Import a Collection

  1. Select the Collection tab from the sidebar.
  2. Click the Menu icon (see image) and select Import or Import from Url.
  3. Now select a file from Postman, Thunder Client, Insomnia, or Open API. import-from-url

How to Convert to Postman Format

  • From the Sidebar menu at the Top (...) — Select Convert To Postman Format.
  • From Command Palette — Via the Convert To Postman Format option.

Keyboard Shortcuts

  • Ctl+Shift+P (From Command Palette):
    • Thunder Client — New Request
    • Thunder Client — Run Last Request
    • Thunder Client — Import Curl
    • Thunder Client — Change Environment
    • Thunder Client — Convert To Postman Format
  • Cmd/Ctrl + Enter — To execute the request.
  • Enter — on request url field to send request.
  • Cmd/Ctrl + s — Save Request without run.
  • Cmd/Ctrl + click — on request in Sidebar will open it in a new tab.
  • Cmd/Ctrl + s — Environment view save data.
  • Cmd/Ctrl + e — Change active environment.
  • Alt+Shft + f — Format Post Body data.
  • Cmd/Ctrl + u — Import Curl.
  • Alt + z — Toggle word-wrap on response.
  • Escape — Cancel response full-screen mode.

VS Code Settings

To see all the VS Code settings for Thunder Client:

  1. Open VS Code settings View, then search for Thunder Client.
  2. From Sidebar View -> Click ... menu at the top, then click Extension Settings.


  • If you'd like to improve documentation, please submit a PR.
  • Suggestions to further improve the product.


  • Basic, anonymized analytics data is collected using vscode-extension-telemetry. No personal or requests data is collected. You can opt-out using VS Code Settings details here.
  • There is no backend or cloud sync; all data is stored locally on your computer.
Open Source Agenda is not affiliated with "Thunder Client Support" Project. README Source: rangav/thunder-client-support

Open Source Agenda Badge

Open Source Agenda Rating