Powerful HTTP and GraphQL tool belt. Free and open source on Mac, Windows, and Linux. Create HTTP requests. Specify URL, payload, headers, and authorization all in one place. Then just hit send. View response details. Get all the details on every response. View status code, body, headers, cookies, and more! Reuse API keys or session IDs. Popular Alternatives to RESTClient for Windows. Explore 24 Windows apps like RESTClient, all suggested and ranked by the AlternativeTo user community. Advanced REST Client (ARC) API testing tool. Which allows web developers to create and test custom HTTP requests. Free Open Source Mac Windows Linux Chrome OS Chrome. Chromium Chrome Web Store. Feb 14, 2019 The only REST client that makes connection directly on socket giving you full control over the connection and request/response headers. Note: You must use valid certificate (for secured connections) to use this app. Get free SSL certificate from letsencrypt.org. Alternatively check 'use XHR' to disable socket and use Chrome's regular connection. Insomnia is a cross-platform GraphQL and REST client, available for Mac, Windows, and Linux. Powerful HTTP and GraphQL tool belt. Free and open. Reuse API keys.
This feature is only supported in the Ultimate edition.
When testing a web service, you can create, edit, and execute HTTP Requests directly in the IntelliJ IDEA code editor.
HTTP Requests are stored in .http and .rest files and are marked with the icon.
HTTP client in IntelliJ IDEA code editor. This feature is only supported in the Ultimate edition. When testing a web service, you can create, edit, and execute HTTP Requests directly in the IntelliJ IDEA code editor. Sep 20, 2017 Nowadays, there are many tools can help handle REST API testing. However, prominent among them are the top 3 including SoapUI, Postman, and Katalon Studio. SoapUI is widely cited as a top choice when it comes to API testing. It is a headless functional testing tool specifically designed for API testing. SoapUI supports both REST and SOAP services.
Support for HTTP files includes the following features:
Before you begin, configure the Proxy settings on the HTTP Proxy page of the Settings/PreferencesCtrl+Alt+S dialog if necessary.
Testing web services is supported via the bundled HTTP Client plugin, which is enabled by default in Settings/Preferences | Plugins.
Creating HTTP request files
You can work with HTTP requests either from scratch files or from physical files of the HTTP Request type. Each file can contain multiple requests, and you can create as many files as needed.
Scratch files can be used to test HTTP requests during development. Scratch files are not stored inside a project, so IntelliJ IDEA can modify them and add additional information about the request. When an HTTP request is executed from a scratch file, the link to the response output file is added below the request and at the top of the requests history file.
Create an HTTP request scratch file
Press Ctrl+Shift+Alt+Insert and select HTTP Request.
Physical files can be used for documenting, testing, and validating HTTP requests. Physical files are stored inside your project, and IntelliJ IDEA will not modify them. When an HTTP request is executed from a physical file, this file is not modified. Information about the executed request with the link to the response output file is added to the top of the requests history file.
Create a physical HTTP request fileRest Api Tools For Windows
In the File menu, point to New, and then click HTTP Request.
You can use the Move refactoring F6 to move HTTP requests from scratches to physical files, as well as between physical files.
Move an HTTP request
Composing HTTP requests
You can type HTTP requests directly in the created HTTP request files using the following general syntax:
Method Request-URI HTTP-Version Header-field: Header-value Request-Body
IntelliJ IDEA uses the HTTP request in Editor format, which provides a simple way to create, execute, and store information about HTTP requests. To get an overview of its possibilities, you can explore the HTTP Requests Collection, which is a handful selection of composed requests.
Open a request from the HTTP Requests Collection
See Exploring the HTTP request in Editor syntax for the syntax and capabilities overview, and HTTP request in Editor specification for the full format description.
To speed up composing HTTP requests, use live templates. For example, gtr expands to a simple GET request; mptr expands to a
multipart/form-data POST request.
Converting cURL requests
If you are working with cURL requests, you can convert them into the HTTP request in Editor format.
Consider the example request:
curl 'http://httpbin.org/' -H 'Connection: keep-alive' -H 'Accept: text/html' -H 'Accept-Encoding: gzip, deflate' -H 'Accept-Language: en-US,en;q=0.9,es;q=0.8'
Upon conversion, this request will look as follows:
GET http://httpbin.org/ Connection: keep-alive Accept: text/html Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.9,es;q=0.8
The following cURL options are supported:
Using environment variables
When composing an HTTP request, you can parametrize its elements using environment variables. For example, instead of providing the host name in your request explicitly, you can use the
{{host}} placeholder. Then you define a set of environment variables in your project holding the desired host definitions. When you execute the request, you choose between defined environments, for example, the host to send the request to:
The selected environment will be used as the default one when Viewing a structure of the request and opening the request in the browser or creating a run/debug configuration for it.
The name of a variable can be arbitrary, but may only contain letters, digits, the underscore symbols
_ , or the hyphen symbols - . A variable can hold the values for the following request components:
Define environment variables
Environment variables are defined in the environment files.
You can manage variables programmatically in your response handler scripts by means of the
client.global.get and client.global.set methods.
Using response handler scripts
With response handler scripts, you can programmatically react to a received HTTP response. By using these scripts, you can automatically process the received data as well as validate it against the conditions that you specify. Response handler scripts are provided as a part of the request within the HTTP request file and are executed as soon as a response is received. To view the response handling examples, open the auth-requests or test-responsesrequests collections.
You can insert a response handler script into your request either in-place or by referring to an external file.
Insert the script into the request
Response handler scripts are written in JavaScript ECMAScript 5.1, with coding assistance and documentation handled by the bundled
HTTP Response Handler library. For in-place scripts, this functionality is enabled automatically. For external scripts, you need to enable it manually.
Enable HTTP Response Handler coding assistance in a JavaScript file
Refer to Configuring JavaScript Libraries for details.
The
HTTP Response Handler library exposes two objects to be used for composing response handler scripts:
To open the HTTP Response Handler library in the editor, position the caret at the library object and press Ctrl+B
Response handler scripts can include tests, which allows you to use the HTTP Client as a testing framework. To create a test, invoke the
client.test(testName, function) method. Inside the test, you can assert a condition by invoking the client.assert(condition, message) method, for example:
GET https://httpbin.org/status/200 > {% client.test('Request executed successfully', function() { client.assert(response.status 200, 'Response status is not 200'); }); %}
Executing HTTP requests
Open a request in the browser
You can open an HTTP request in the browser specified on the Web Browsers page of the Settings/Preferences dialog (Ctrl+Alt+S). Select your system default browser or the one of your choice.
Do any of the following:
Working with HTTP Request Run/Debug Configurations
You can execute HTTP requests by using run configurations of the HTTP Request type. With the run configuration, you can execute a request at any point, add it to the Services tool window, or a compound configuration.
Refer to Working with Run/Debug Configurations for details.
![]() Create an HTTP Request run/debug configuration
When you execute an HTTP request from the editor, IntelliJ IDEA automatically creates a temporary run/debug configuration with the request parameters. A temporary run/debug configuration works the same way as a permanent run/debug configuration. You can change its settings using the Run/Debug Configuration dialog and optionally save it as permanent.
Save a temporary HTTP Request run/debug configuration
Do any of the following:
Execute a request using a run/debug configuration
Do any of the following:
Viewing responses from web services
When you execute an HTTP request, IntelliJ IDEA automatically saves the response into a separate file under the .idea/httpRequests/ directory. You can view the 50 most recently stored responses and navigate to the corresponding files using the requests history. If the request was executed from a scratch file, the link to its response output is also added below the original request:
The cookies received through a response are automatically saved into the dedicated http-client.cookies file under the .idea/httpRequests/ directory. The number of cookies that can be saved is limited to 300. The name and value of a cookie are automatically included in each subsequent request to the URL that matches the domain and path specified for the cookie, provided that the expiry date has not been reached.
If necessary, you can prevent saving the received cookie to the cookies jar by adding a comment line with the @no-cookie-jar tag before the request.
View a received response
Open a response file in the editor
Compare responses in a scratch file
When a request is executed from a scratch file, the link to the response output file is added below the original request.
Do any of the following:
Compare responses in the requests history
When a request is executed from a physical file, the link to the response output is added to the requests history.
The two response files will be opened in the Differences viewer allowing you to compare their contents:
Viewing requests history
IntelliJ IDEA automatically saves the 50 recently executed requests into the http-requests-log.http file, which is stored on the project level under the .idea/httpRequests/ directory. Using the requests history, you can quickly navigate to a particular response as well as issue any request again. If a request is issued again from the requests history, its execution information and the link to the response output are added to the top of the requests history file.
Open requests history
Click in the top-right corner of the editor or choose Tools | HTTP Client | Show HTTP Requests History from the main menu.
If necessary, you can prevent saving a request to the requests history by adding a comment line with the @no-log tag before the request. This can be helpful in case a request contains some sensitive data, and you don't want to log it.
Configuring proxy settings![]()
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |