February 2022 Summaries

Mock servers, as described in the Postman API Platform, are tools that simulate API requests and responses, facilitating smoother development processes by allowing teams to work in parallel without waiting for full API integration. They are particularly useful for overcoming delays caused by debugging APIs or waiting for endpoints to be fully configured, enabling rapid development and iteration by providing example data that mimics what a production instance would deliver. Mock servers prove beneficial for both API producers and consumers, particularly in collaborative environments where multiple teams, such as frontend and backend developers, need to work concurrently. By using mock servers, developers can start working with expected API responses early in the design phase, avoiding disruptions and enabling a more efficient workflow until the real API is production-ready.

The inaugural API Fest, hosted by the Postman Student Community from January 26-29, 2022, provided a dynamic platform for over 900 participants from 28 countries to enhance their understanding of API-first development through a series of workshops and team-based projects. The event, which saw a significant increase in participants' API knowledge from an average self-assessment score of 2.47 to 4.1 out of 5, was structured around interactive sessions led by experts like Postman Chief Evangelist Kin Lane and Student Community Manager Claire Froelich. These sessions focused on API schema design and coding, respectively, and were complemented by mentorship from industry professionals from companies such as Twitter and Capgemini. The festival culminated in the recognition of the top 10 student projects, showcasing applications ranging from library finders to restaurant management systems, all developed by teams guided by 34 mentors. The entire event was orchestrated by Postman Student Leaders, emphasizing a peer-driven approach to learning and development in the API sphere.

Postman has announced its API Platform now supports OpenAPI 3.1 files, the latest version of the OpenAPI specification, which enhances its functionality by allowing users to describe webhooks, integrate fully with JSON Schema's latest draft, and identify API licenses via the SPDX identifier. This update complements Postman's existing support for previous OpenAPI versions and other API specification formats such as WSDL, RAML, and GraphQL. Users can import, edit, and generate collections from OpenAPI 3.1 files within Postman, and also create new documents directly in the platform. Postman invites feedback from users through GitHub, the Postman Community forum, or via email, emphasizing community engagement around this new feature.

Postman is committed to making API development inclusive and accessible, as exemplified by their public workspaces that encourage global collaboration. During Black History Month, a particular initiative focused on creating a public workspace with APIs related to Black history and culture, highlighting the scarcity of easily discoverable APIs in this domain. Despite challenges in finding such APIs, the workspace now includes resources like the Black History Facts API, Igbo API, SeatGeek API, 8:46 API, and Twitter API, each serving unique purposes ranging from education on Black history and language preservation to tracking live events and social issues. The goal is to foster community collaboration to expand this repository, inviting developers to contribute further to the Black History/Culture APIs public workspace.

Postman public workspaces have become crucial for API producers aiming to enhance the adoption and ease of use of their APIs by linking them effectively with developer documentation. Effective strategies include embedding links within developer docs that direct users to Postman collections, using Run in Postman buttons for seamless interaction, and bundling collections with corresponding environments to simplify the process for users. API producers like MongoDB, Datadog, and Twilio illustrate best practices by providing step-by-step guides and optimizing searchability within both Postman and their documentation. The use of Run in Postman buttons is emphasized as a superior solution, allowing users to fork collections, which establishes a connection with the parent collection and ensures they receive updates. This approach, alongside encouraging users to "watch" workspaces, enables better communication of updates and helps producers monitor API performance through user engagement metrics. By prioritizing user empathy and reducing friction in accessing API resources, producers can significantly enhance the developer experience.

Postman audit logs provide a detailed record of system and user activities, enabling admins of Postman teams to monitor how their organizations utilize the Postman API Platform. These logs allow admins to track events such as updates or removals of custom authorization schemes, changes in user roles, and team member invitations. Accessible via the Postman API, these logs can be integrated with security information and event management (SIEM) tools for customers on the Professional and Enterprise plans. Each audit log event includes attributes such as a unique identifier, IP address, user-agent, action performed, timestamp in ISO 8601 format, actor details, and a description of the event. Users can access their team’s audit logs through the Postman app or the Postman Public Workspace, where they can execute requests to retrieve specific audit log information. The Postman Trust Center also provides resources to enhance organizational security and data protection.

Postman has announced the open-beta release of its uptime monitor, a new feature designed to simplify API endpoint uptime monitoring by continuously testing the availability of public HTTP(s) domains and alerting users to system-outage incidents. Unlike the previous process, which required creating Postman Collections, requests, and environments, users can now directly create an uptime monitor by specifying a name and endpoint URL. This streamlined process aids software developers, DevOps engineers, and business program managers in quickly detecting system outages. The feature, only available in the web-based version of Postman during the open beta, allows teams to specify email notifications for outages and is free to use with limitations during this period. Feedback is encouraged through Postman's GitHub repository to help improve the feature.

Postman Collections are integral to the Postman API Platform, offering efficient organization, management, and documentation of APIs. Key features of Postman Collections include the ability to move, duplicate, and share collections, which enhance user collaboration and workflow management. The move feature facilitates seamless transfer of collections between workspaces, provided the user has the requisite editor access, while the duplicate feature allows users to create untouched copies of collections for parallel development. Sharing collections is essential for team collaboration and can be achieved through links or by moving collections to shared workspaces, with specific access permissions required. These functionalities not only apply to collections but also extend to other elements within Postman, such as APIs, environments, mocks, and monitors, thereby broadening the scope of collaborative and efficient API management.

Postman has enhanced its public workspaces to facilitate real-time collaboration among API producers and consumers worldwide, transcending organizational and team boundaries. This update allows users to see and interact with other Postman users in the same public workspace, regardless of team affiliation, thereby fostering instant idea sharing. Users' public profiles are visible in the workspace, although those who prefer privacy can remain anonymous. Importantly, this update does not change the functionality of private and team workspaces, which still support real-time collaboration exclusively among team members. This development is part of Postman's effort to make public workspaces a more powerful tool for community engagement and collaboration, and the company is seeking user feedback to further enhance these capabilities.

Postman has introduced a WebSocket echo service to allow users to explore WebSocket requests using sample endpoints, enhancing their understanding of this newly supported feature. The service includes two distinct WebSocket servers: one for Raw WebSocket connections and another for Socket.IO connections, each designed to facilitate learning by providing practical examples of query parameters, headers, and message formats, as well as event handling and listening. This initiative aims to assist developers within the Postman community in navigating WebSockets by enabling them to test and troubleshoot their WebSocket APIs effectively. Users are encouraged to engage with the Postman Community forum for discussions, provide feedback through the GitHub issue tracker, and consult the Learning Center documentation for further guidance on using Postman for WebSocket APIs.

Postman has enhanced its API management capabilities by enabling each API version to have its own specification, repository, and collections, making it easier to sync with Git-based version control systems like GitHub. This process starts with creating or importing an API specification into Postman, connecting it to a Git repository, and using Git to synchronize changes between the repository and Postman. Once connected, teams can generate collections from the API specification to serve as documentation, tests, or mock servers, and these collections can be kept aligned with the specification through schema validation. Users can manage different API versions and releases within Postman, allowing for either manual updates or the creation of new versions, depending on the scope of changes. This flexibility supports both minor and major updates, with options to retain or regenerate linked collections. Postman also facilitates the designation of releases, which act as milestones in the API lifecycle, and can be mapped to Git release tags for better tracking and communication with team members and consumers.

Postman, a company dedicated to addressing user needs and enhancing user experiences, is actively seeking insights from its community to improve its services, which have grown to include over 17 million users globally. With the launch of the new Postman API Platform in September 2021, the company is eager to gather feedback through its UX Research Program to understand how users are engaging with the platform's latest features. Postman encourages users to explore blog posts by Co-founder and Head of Product Abhijit Kane, which highlight recent advancements like powerful integrations and a reimagined API-first workflow for developers and testers. The company invites users to share their experiences and impressions by signing up for the research study, aiming to refine and enhance the platform for a global audience.

Continuous monitoring is crucial for API success, prompting companies to invest in tools that ensure optimal performance and observability. According to Apigee's 2021 report, 20% of surveyed companies prioritized investment in API operations and monitoring. Postman's latest release enhances API monitoring by integrating with analytics, incident management, and messaging tools, allowing users to view essential data in a single dashboard. Users can connect Postman to external tools like Statuspage, Opsgenie, PagerDuty, Splunk On-Call, Datadog, and Slack to streamline incident management and performance metrics. This integration facilitates efficient communication and quick response to API issues, ultimately aiming to improve API monitoring effectiveness.