Using a multi-environment structure with API Management (APIM) gives you more control over how your API changes are developed, tested, and released to your API consumers. Your environments in the APIM console mirror the ones in the Celigo platform, so you can manage APIs per environment without configuring anything separately in the console. This article explains how the two stay in sync, how to set an environment prefix, and how pushing APIs works across environments. For the basics of environments, see Multiple environments overview.
With multiple environments and API Management, you can:
- Access the same environments in the APIM console that you have in the Celigo platform.
- Define environment-specific prefixes for your portal and gateway URLs for more flexibility in your DevOps workflow.
- As an admin, get automatic access to all APIs in an environment in the APIM console whenever you're newly invited to that environment in the Celigo platform.
Create a new environment with API Management
The APIM console reflects your changes automatically whenever you create a new environment in the Celigo platform. You don't need to change anything in the APIM console — create your new environment in the Celigo platform, and it appears in your APIM console.
To create a new environment, follow the steps in Create and manage multiple environments. When you create it, set an Environment prefix for APIM, which generates the Developer portal and API gateway URLs.
Platform and APIM console parity
When you create your environment, the following occurs:
- The Developer portal and gateway URLs are created automatically, reflecting the name you used when creating the environment.
- An API token is created automatically for your new APIM environment.
- New users added to the new environment can automatically access all the APIs in the new environment.
To access your newly created environments, open your APIM console from the Celigo platform. The environments are available at the top of the page.
When you push an API from the Celigo platform, it's pushed to the environment you're using in the platform. You can't push an API from a non-production environment to a Production environment.