You can create multiple versions of a managed API or custom API, choose the default version, and delete a version.
When you create a version of an API, API Manager creates an additional API with the same name. Each version appears as a separate entry on the API Registry page. Default appears next to the entry of the default version on the API Registry page.
If a version of an API is not the default version, API Manager adds the version to the API URL of the API. API Manager doesn't add the version to the API URL of the default version.
API consumers can invoke all versions of an API with a URL that contains the version, including the default version. A URL that doesn't contain the version always invokes the default version.
In the API details window, the API URL of the default version doesn't include the version. If you choose a different version as the default version, API Manager adds the version to the API URL of the previously default version, and removes the version from the API URL of the current default version. Be sure to notify API consumers of the changes in API URLs.
When you create a new version of an API, you can choose whether or not API Manager applies the policies of the API version that the new version is based on to the new version. Policies include authentication method and API-specific policies. If you choose not to copy the policies from the original version, configure policies for the new version.
When you copy a policy of a managed API where token authentication is enabled, the tokens that the original version uses don't apply to the new version. Perform one of the following actions:
•If the original version uses OAuth 2.0 authentication, add the new version of the managed API to the OAuth 2.0 client and re-generate the token.
•If the original version uses JSON Web Token (JWT) authentication, create JWT tokens for the new version.
If an API has multiple versions, you can delete any version of the API other than the default version. To delete the default version of the API, choose a different version as the default version.
Creating an API version
Create a new version of a managed API or custom API. An API can have up to three versions.
1In the API Registry page, select Managed APIs.
The API Registry page lists all the available managed APIs and custom APIs.
2Click to open the Actions menu of the API, and select Create New Version.
The Create New Version page appears.
3 Enter a unique version.
Version can contain up to 10 characters including any letter on the ASCII table, any digit, and the special characters . _ and -. It cannot contain spaces and any of the following characters: / ` " ' < > & : ~ ! @ # ; % ^ * + = { } | , \ $ ? ( )
Note: Version cannot be "t" because it is reserved for Informatica internal use.
4By default, the option Copy policies from version <version> is selected. You can deselect this option.
If this option is selected, API Manager copies policies from the API version that the new version is based on, including the authentication method of the original version and the API-specific policies that are configured for the original version.
5Select a service for the version from the list of available services.
6Click Create.
API manager creates a new version of the API.
The version of the API appears in the list of APIs. The service that you created the version from no longer appears in the list of available services.
7To set the version as the default version of the API, on the API Registry page, click to open the Actions menu of the new version and select Set Version as Default.
Default appears next to the version on the API Registry page. API Manager adds the version to the API URL of the previously default version, and removes the version from the API URL of the current default version. Notify API consumers of the changes in API URLs.
Changing the default version of an API
When you change the default version of a managed API or custom API, API Manager adds the version to the API URL of the previously default version, and removes the version from the API URL of the current default version. Be sure to notify API consumers of the changes in API URLs.
You cannot change the version of an active API. To change the version of the API, deactivate it first. For more information, see Deactivating and activating an API.
1In the API Registry page, select Managed APIs.
The API Registry page lists all the available managed APIs and custom APIs.
2Click to open the Actions menu of the API, and select Set Version as Default.
3Click OK to confirm the action.
The API is set as default. Default appears next to the version on the API Registry page.