Skip to main content

Using HTTP Files in VS Code with REST Client

I regularly switch between multiple IDEs, mostly VS Code and Visual Studio but sometimes also Rider or Cursor. One of the Visual Studio features I miss when using VS Code is the support for HTTP files.

What if I told you that there is a way to use HTTP files in VS Code? Enter the REST Client extension for Visual Studio Code, a lightweight, powerful tool that lets you test APIs without ever leaving your editor.

What is the REST client extension?

Similar to the HTTP support in Visual Studio, the REST Client extension allows you to send HTTP requests and view responses directly in VS Code. It's minimal, scriptable, and integrates seamlessly into your existing workflow. It offers the same functionality as in Visual Studio and more:

  •   .http and .rest file extensions support
  • Syntax highlight (Request and Response)        
  • Auto completion for method, url, header, custom/system variables, mime types and so on
  • Comments (line starts with # or //) support
  • Support json and xml body indentation, comment shortcut and auto closing brackets
  • Code snippets for operations like GET and POST
  • Support navigate to symbol definitions(request and file level custom variable) in open http file
  • CodeLens support to add an actionable link to send request
  • Fold/Unfold for request block

Installation

Installing REST Client is straightforward:

  1. Open VS Code
  2. Go to the Extensions marketplace (Ctrl+Shift+X / Cmd+Shift+X)
  3. Search for "REST Client" by Huachao Mao
  4. Click Install

That's it! You're ready to start making API calls.

Creating your first request

Create a new file with the .http or .rest extension. Let's call it example.http:

 

As soon as you save the file, you'll notice a "Send Request" button appears above the GET line. Click it, and voilà! The response appears in a new pane to the right, complete with status code, headers, and body.

Working with multiple requests

Of course you typically want to manage multiple API calls. Separate requests using three hash symbols (###):

Important: Notice the empty line between the headers and the JSON body in the POST request. This blank line is required by the extension.

Adding variables

Define variables at the top of your .http file for values that remain constant throughout:

 

What’s next?

This is only the tip of the iceberg of what is possible with the REST Client extension. there is a lot more to discover. I would recommend giving the extension a try. It transforms VS Code into a capable API testing tool without sacrificing the simplicity and focus that make it a great editor. By keeping your HTTP requests in .http files alongside your code, you create living documentation that your entire team can use and maintain.

Whether you're building a new API, integrating with external services, or just need to quickly test an endpoint, REST Client keeps you in your flow and makes API testing feel like a natural part of your development process.

More information

Use .http files in Visual Studio 2022 | Microsoft Learn

REST Client - Visual Studio Marketplace

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...