June 2015 Summaries

Postman provides multiple ways to create HTTP requests, but inspecting the exact request and response payloads can be challenging, requiring the use of Chrome DevTools. To view these details, users must first enable DevTools, a set of debugging tools built into Chrome. There are three primary methods to make requests in Postman: using the request builder, using the collection runner, and using Postman with the Interceptor enabled. When using the request builder, users can inspect the request and response by accessing the Network tab in DevTools from the main Postman window. For the collection runner, DevTools must be opened specifically for that window to view each request and response during a collection run. The Postman Interceptor, a companion extension, allows for additional functionality like adding cookies, and requests with the Interceptor enabled are managed through its DevTools window. This setup provides a comprehensive way to debug and verify API calls within Postman.

Newman, the command line companion for Postman, has been moved to the Postman Labs GitHub organization, a change that predominantly affects its location without altering its functionality. GitHub's repository transfer process ensures that all links, including issues and forks, are redirected to the new location, so users with a local clone of the repository can continue using it without interruption. However, to avoid confusion, users are advised to update their git remote URL to the new address. If any access issues arise, users are encouraged to reach out for assistance.

Postman Collections have evolved from a simple organizational tool within the Postman client app to a versatile format utilized across various platforms, such as build systems and continuous integration environments, thanks to the Postman Collection Format and Newman, which allow collections to run from the command-line. The format, which is based on JSON, facilitates collaboration among distributed teams by enabling the sharing of collections that outline web services, along with their documentation and tests, thereby streamlining the API development lifecycle. The current v1 format is being enhanced to v2 to improve human readability, portability, and extensibility, allowing for a more intuitive structure that supports the entire API lifecycle, from design to maintenance. The new format will feature more intuitive referencing, simplified sub-structures called "units," and expanded capabilities for variables, aiming to minimize complexity while ensuring versatility and adaptability across different toolchains. This evolution seeks to cover all functionalities of the original format while integrating additional features for enhanced API definition and documentation, with the possibility of community collaboration in its ongoing development.