The Version Details page is the space where you can view information about a version of the API, the assets it contains, and permissions. Besides performing all lifecycle actions for an API published on the API Portal, you can manage API policies for the API version.
Created: The date when the API is created.
Owner: The user who owns the Asset. Typically, the owner inherits the asset when it is moved or the creator is no longer a user in the Org.
Updated: The time the API Version is last updated.
Versions: The status of the API version.
Policy: The policies applied to the API Version. Click the policy name to display the policy’s Settings dialog.
Type: The type of the API policy.
Owner: The owner of the API policy.
Update: The time the API policy is last updated.
Status: Indicates if the API policy is Enabled or Disabled. You can enable or disable an API policy in the policy’s Settings dialog.
Description: The API’s description, which is added during the creation of the API or the API Version.
Tags: Metadata added to the API and API version.
To view the Version Details page,
In the API Manager, click the API name.
Go to the Versions tab.
Click the version number of the API version you want.
You can edit the description and tags for an API Version without republishing the API. You can also change the Snaplex if the API version is unpublished.
Navigate to the target API, and click the version to edit.
Click Edit Details, and update the following fields:
In 4.26, to change a Snaplex for an API Version, you must create a new version, update the Snaplex, and then publish a new version of the API. Clicking Edit Details from the API > Versions page displays the Server field for selecting another Snaplex, but the field is disabled.
Generating the Specification for your API
To preserve the API specification used in the API version published in the Developer Portal, click Generate OAS 2.0 Spec. The generated specification is in the Open API Specification (OAS) 2.0 format, and the API consumer can examine its contents when viewing the API’s documentation in the Developer Portal.
Even if the API was created with OAS 3.0, the generated specification is still in OAS 2.0 format.