![Postman Postman](/uploads/1/2/4/1/124155022/896772425.png)
Is a powerful HTTP client for testing web services. Created by Abhinav Asthana, a programmer and designer based in Bangalore, India, Postman makes it easy to test, develop and document APIs by allowing users to quickly put together both simple and complex HTTP requests.
Postman is available as both a Google Chrome Packaged App and a Google Chrome in-browser app. The packaged app version includes advanced features such as OAuth 2.0 support and bulk uploading/importing that are not available in the in-browser version. The in-browser version includes a few features, such as session cookies support, that are not yet available in the packaged app version. At publication time, the Postman REST Client is one of the highest-rated productivity apps in the Chrome Web Store, with more than 348,000 unique users (for both versions), and more than 63,000 collections shared via Postman (more on that later). This post is an in-depth review of the Postman Google Chrome highlighting the key features that make Postman a must-have tool for API developers and consumers at all levels of experience. In our review of the Postman Google Chrome Packaged App, we found that Postman has a very clean and intuitive user interface, with most key features accessible within one click. The learning curve for using the program is very low; most users should be able to start building and testing API calls very quickly.
If you are using 64 bit windows then select x64 and if you are using 32 bit system then select x86. Default value is x64. 2) Choose the Operating System on which you want to install PostMan and click on “Download“ button. Since I have got Windows 64-bit machine, I am going to install x64-Windows.
One big reason for Postman’s ease of use is its automation capabilities: It helps to automate the process of making API requests and testing API responses, allowing developers to establish a very efficient workflow. History / Auto complete. All API calls sent using the Postman app are stored in history (the calls are displayed in the left sidebar), allowing them to be easily loaded into the response viewer at a later time. Prior API calls can be loaded into the response viewer by simply clicking the API call in the history list. Auto-complete suggestions are conveniently displayed in drop-down menus in many places throughout the app, including URL input fields, header fields and header presets.
These features save developers time by eliminating the need to retype entire API calls or other pertinent API information. Easy organization. Postman provides an environment in which tests can be written and run without any additional setup.
The tests are basically JavaScript code snippets that can be used to test API responses, ensuring that that they have met the conditions as specified in the test code. A list of commonly used test snippets is displayed on the right side of the text editor so that users can add tests to API requests with just one click. The test snippets available from within Postman include (but are certainly not limited to) checking if the response body contains a string, checking if response time is less than 200 ms, checking if status code is 200 and using Tiny Validator for JSON data. Environment and global variables can be set within Javascript, which allows requests to be chained together. Users an import a CSV or JSON file that can then be used as mock data when running tests.
![Windows Windows](/uploads/1/2/4/1/124155022/162500162.png)
Test results can be viewed in the tests tab of the response viewer, as well as in the Postman collection runner. This feature allows developers to test API requests and complex scenarios without having to write a lot of additional code. Indeed, developers will likely find that Postman significantly cuts down on the amount of code they need to write themselves.
This will not only save a lot of time, but will also help developers new to API testing to quickly understand how API requests work. The test editor and runner is available as part of the Postman “Jetpacks Upgrade.” There is a one-time fee for installing the Jetpacks upgrade; the upgrade is free to anyone who has already donated to the Postman project. Collection runner. Environments allow API calls to have different setups, such as local machine, development server or production server. Environments also allow sensitive data like API keys and passwords to be separated from collections. Such data can be stored in the local environment and represented as variables. When sharing collections, variables are included in the API calls instead of the API keys.
All data inside Postman is stored in a local database so nothing is shared without the explicit permission/intent of the user. This model helps ensure that users have complete control of their data, and that passwords, API keys and other sensitive API data are secure. Authentication support / OAuth 2.0 support.
For example in a recent Box blog post, Box created and provided links to two collections of API calls: one collection for the Box Content API and the other for the Box View API. By providing these collections of APIs, Box has made it much easier for developers to get started on and become familiar with the available features of its APIs. Postman Wish List The Postman REST Client has many other useful functions and features, including keyboard shortcuts, header presets, keyword filter for history and collections, bulk upload/import, and the ability to save API responses to disk. Postman also includes many features designed to dramatically reduce the time needed to test and develop APIs. With all of that said, I’d like to see future versions of Postman include a built-in validator for JSON and perhaps also for XML. Sometimes API responses are returned with badly formatted XML or invalid JSON, which can cause parsing issues.
The ability for Postman to automatically validate API responses or provide an option to validate JSON / XML responses from within the app would be helpful. (It should be noted that the Postman test editor and runner does include the Tiny Validator library, which can be used to validate JSON Schema and make sure that the data structure is correct.) It would also be nice if Postman could save files and settings (similar to functions in Google Chrome sync) across devices. Collections can currently be saved to getpostman.com.
However, we’d also like to see the ability for Postman collections to be shared using file storage services such as SmartFile, Box or DropBox. The Wappwolf API may also be an option for implementing collection sharing via file storage and sharing services in the Postman app. Finally, it would be nice to be able to reorder collections in the same way that API calls can be reordered, via drag and drop. Currently, API calls listed in the left sidebar can be reordered via drag and drop, but collections cannot. By default, collections are listed in the left sidebar in alphabetical ordert. Conclusion Postman REST Client is a real time saver, making it easier for developers to test and work with APIs. Indeed, Postman is a must-have tool for developers that regularly work with APIs–from developers just beginning to consume APIs for their web and mobile development projects to experienced developers who design, test and release APIs for public consumption.
For more information and to download the Postman REST Client, visit GetPostman.com.
I have problems with my installed Postman on a Windows Server 2012 R2 (x64 Version 6.3, build 9600). First of all, I have downloaded and successfully installed (and also later removed) different versions of Postman: 6.1.4 (tried x86 and x64) and 6.1.3 (tried x86 and x64) Fact: I access my Windows Server 2012 R2 instance through a nested RDP like this My computer - Server 1 - Windows Server 2012 R2 Edit 1: Image depicting how I access my Windows Server 2012 R2.
Strange look and behaviour: Same result with every tried Postman-version. Whats the problem here? I do not know about any other application on the server that have this GUI problem. I had this same issue, and I solved it by setting the POSTMANDISABLEGPU environment variable, as described here:. For it to work you will have to add an environment variable POSTMANDISABLEGPU=true. Open advanced system settings.
In the Advanced tab click Environment Variables. Add a new variable. Logout and Login back or Restart your PC Note that my scenario is a little different: I'm running Server 2012 in VMWare Fusion 10.0 on a Mac OS High Sierra.
But my experience was identical to yours.