Using multiple environments with API Management (APIM) gives you more control over how API changes are developed, tested, and released to your API consumers. The environments in the APIM console mirror the ones in integrator.io, so you manage APIs per environment without configuring anything separately in the console. This article is for API developers and administrators. It explains how the two stay in sync, how to set an environment prefix, and how pushing APIs works across environments. For what environments are, see Multiple environments overview.
With multiple environments and API Management, you can:
- Work with the same environments in the APIM console that you have in integrator.io.
- Define an environment-specific prefix for your Developer portal and API gateway URLs.
- As an administrator, get access to all APIs in an environment in the APIM console as soon as you're invited to that environment in integrator.io.
Create an environment with API Management
Create the environment in integrator.io, and it appears in your APIM console — you don't need to change anything in the console. When you create it, set the Environment prefix for APIM, which generates the Developer portal and API gateway URLs. See Create and manage multiple environments.
When you create the environment:
- The Developer portal and API gateway URLs are created automatically, using the prefix you set.
- An API token is created automatically for the new APIM environment.
- Users added to the environment can access all of its APIs.
Work in an environment in the APIM console
Open the APIM console from integrator.io. The environments are available at the top of the page, and you switch between them the same way as in integrator.io. See Switch between environments.
When you push an API from integrator.io, it's pushed to the environment you're working in. You can't push an API from a non-production environment to Production.