You can now attach environments to APIs in the Private API Network
We are pleased to launch support for attaching environments to the APIs that you publish to the Private API Network.
Until now, you could only attach environments while publishing collections to the network, allowing consumers to resolve the variables to the relevant values while looking at the collection documentation. But this support was missing for APIs, whose available environments were listed in the parent workspace.
What’s changing?
Now, you have the ability to select environments while publishing APIs to the network, as well as update the environments for APIs already on the network.
Why the change?
Consumers on the Private API Network need to be able to send requests as quickly as possible. Environments help them do so because they can resolve variables and let consumers successfully call an endpoint without having to understand the specifics of the API (i.e., authentication method or the right host for a given deployment, like sandbox/staging).
However, with workspaces being a place where a lot of APIs and environments exist, it can be challenging for people without the right context to determine which environments are meant to be used with a given API. This new ability to attach environments to APIs solves that confusion.
How to get started
You can attach environments to your API by these methods in the Postman API Platform:
-
While publishing the API to the Private API Network from the workspace.
-
Using the bulk add flow from within the Private API Network.
-
Choosing the select environment action on the published API.
You can also use our Cloud APIs to attach environments.
What do you think about this topic? Tell us in a comment below.