These are all of the actions available across all the lifecycle blueprints available in this site.
The Postman API builder allows for the editing of Swagger and OpenAPI definitions in a web or desktop based API design environment, providing autocomplete and validation fo the OpenAPI.
OpenAPIs can be edited within open source editors and API design tooling, allowing for editing of OpenAPIs outside of the Postman platform, then synced for better automation.
Change the visibility of a workspace and it's contents to be accessible only internally by team members who are invited.
Change the visibility of a workspace and it's contents to be public.
Change the visibility of a workspace and it's contents to be accessible only internally by teams.
Change the stage of where an OpenAPI is at in it's lifecycle.
Comment on a specific collection.
Comment on a specific OpenAPI.
Connect an OpenAPI to a Bitbucket repository.
Connect an OpenAPI to a Github repository.
Creating a new OpenAPI in Postman API builder, starting with a new API from scratch, hand designing what an API will actually do.
Create a new version of an OpenAPI for editing.
Export a collection for use outside of the Postman platform.
Export an an environment so it can be used outside the platform.
Export an environment to use outside of Postman.
Fork a specific collection.
Fork an an environment to make a working copy.
Generating client side code from OpenAPI definitions.
Generate a collection from an OopenAPI.
OpenAPI allows for the automation of contract tests for each API, helping increase the coverage for contract tests without much more work.
Generating API documentation from an OpenAPI is a common and quick way to produce documentation that helps developers understand what is possible with an API.
Generating API documentation from an OpenAPI is a common and quick way to produce mock server that helps consumer learn about and see what an API does without actually using in production.
Import a collection into a workspace.
Generate an OpenAPI from Collection
Generating server side code from OpenAPI definitions.
Generating API documentation from an OpenAPI is a common and quick way to produce tests that helps verify an API is doing what it should be doing.
OpenAPI files can be imported into Postman to create a new API, importing via upload, URL, repo, or pasting in the raw text of each OpenAPI.
Azure DevOps Server is a Microsoft product that provides version control, reporting, requirements management, project management, automated builds, testing and release management capabilities.
PingFederate is an enterprise federation server that enables user authentication and single sign-on.
Invite a team member to a specific workspace.
Applying standardized rules to lint an OpenAPI definition within the Postman API Builder, returning assertions regarding the design of the API.
Manage the roles for a collection.
Manage the roles for an environment.
Mange the roles for an OpenAPI.
Generate a mock server for a collection.
Schedule a monitor to run for a collection.
Publish an OpenAPI to a private network.
Manually running a collection.
Share a collection with another workspace.
Share a collection as JSON using a link.
Share a collection by generating a Run in Postman button that can be embeeded on any site.
Share a environment with another workspace.
Share an OpenAPI to a workspace.
Sync a specific collection to a Github repository.
The Postman API allows for the syncing of APis with existing systems, providing the ability to keep changes to each OpenAPI up to date wherever it is needed.
Sync an OpenAPI to any AWS API Gateway stage.
Using the Github integration any OpenAPI can be synced to a Github repository, allowing for the OpenAPI to be kept up to date within Postman as well as a Github repository.
Watch a specific collection.
Watch a specific OpenAPI.
This provides a link back to the home page if you need it.