What is the timeline for Postman’s journey to becoming an API platform?

[kinlane]

This is a discussion around the ongoing timeline of Postman becoming an API platform, supporting discussion and evolution around the answer to the question:

• 2013 - Client, Scripts, and Testing - Life began as a browser bases solution for testing and debugging APIs, helping developers understand how APIs work or do not work, then saving that understanding as a reusable, sharable collection that can be run by others.
• 2014 - Runner and CLI Runner - Collections become a standardized way to define, save, and then run one or many API requests that includes scripting for automation, allowing collections to be run on the desktop or via a command-line interface and CI/CD.
• 2015 - Documentation & Code Generation - Documentation emerges as a priority, expanding the ability for developers to publish shareable and embeddable documentation that also has a variety of code snippets in different programming languages.
• 2016 - Github & GitLab Integration - Source control integration for developers becomes important, allowing Postman to be more tightly linked to the developer’s existing software development lifecycle, allowing artifacts and tests to be kept in alignment with source control.
• 2016 - APM, Messaging Integration - Following source control, the need to integrate with existing APM, notification, and messaging systems became an important part of developers’ workflow to produce and consume APIs as part of their work.
• 2016 - Monitoring - Being able to schedule the monitoring of collection and extend the automation introduced by runners, and at the command line and CI/CD pipeline level, allowing contracts, performance, integration, and other tests to be monitored.
• 2017 - Mocking  - Mocking is an essential part of the API lifecycle, and as part of testing, so Postman introduced the ability to deploy mock servers as defined by a collection and the examples it contains providing a simple way to create static mocks of APIs.
• 2018 - Team Workspaces, Comments, and Search - Acknowledging the need for closer collaboration across teams, workspaces were launched, as well as the ability to comment on collections, and search across workspaces, APIs, and collections.
• 2019 - Builder - With the increased usage of Postman to not just consume and test APIs, but also to deliver APIs, the API Builder was launched, allowing APIs to be designed and developed using OpenAPI, RAML, and GraphQL across team workspaces.
• 2019 - Interceptor - To support the reverse engineering of the existing APIs that exist behind web applications Postman interceptor was launched, allowing web traffic in Chrome to be captured and then used to define a Postman collection within a workspace.
• 2019 - Public Network - The public API network was launched to support the needs of public API producers needing to attract new users, but then also provide a public catalog for API consumers to use when looking for APIs to use in their applications.
• 2020 - Reporting - Reporting was launched to support the needs of the enterprise, providing a way for leadership to see activity across teams, workspaces, and APIs, helping understand activity and move towards more governance of API operations.
• 2020 - Private Network - The private API network was launched to support the need for enterprise organizations to have a single internal catalog where teams can publish and discover the APIs and microservices that are being developed across teams and workspaces.
• 2020 - Public Workspaces - The ability to change the visibility of a workspace to be publicly available was introduced to support the needs of API producers when it comes to engaging with consumers, allowing them to view, fork, and engage with their APIs.
• 2020 - Websockets - With the introduction of WebSockets, the platform signaled a migration towards being a multi-protocol API platform, supporting WebSockets, and socket.io, but laying the groundwork for gRPC, and support for other protocols.

Please add anything you think should be added, changed, or evolved, and let's keep the discussion going around this important timeline, which reflects the journey of our customers.