Skip to end of banner
Go to start of banner

Managing Versions of Your APIs

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 68 Current »

In this article

Overview 

You can create and manage multiple versions of your APIs. A version of an API contains SnapLogic assets such as Pipelines, Tasks, and Open API Specification files. Clicking an API on the API Details page opens the Version Details page, where you can view details about the version and add API policies. You can also search through assets in a Version and view Permission sets.

When you are viewing an API version, you can navigate to the API Details and API Management landing page by clicking the respective folders in the folder path.

The following example illustrates the path of an API version:

API Manager - /apim/API_Test/1.1

From this view, you can click on any component in the path to navigate to that level of the API Management hierarchy:

  • API Management > API Manager: Landing Page

  • API: API_Test

  • Version: 1.1

Prerequisites

  • Your Org must have a subscription to the API Management feature; otherwise, the API Management UI is not enabled.

  • You must have Write permissions to create an API.

API Manager

You can navigate to the API Manager console by clicking Manager > API Management > API Manager.

APIM Manager

Creating an API Version Using Design First

  1. Navigate to API Management > API Manager, and click the target API to display the API Details page.

  2. Click the Versions tab, then click (blue star)  to display the Create Version dialog window.

  3. In the Create API version dialog window, import the API Specification by selecting one of the following options, then click Continue:

    • Select Upload File to choose a file from your local machine. Both JSON and YAML file formats are supported.

    • Select Enter URL to refer to the API specification by URL.

  4. Select/deselect the Import Configuration options, then click Import and Continue.
    The options for import are selected by default.

    • Create Specification: Select to include the specification as a File Asset in the API. Both Deselect to omit the specification file you uploaded.

    • Create Endpoints from Path: Select to include all default Assets for this API. Deselect to leave the API an empty container for you to provide the Assets later.

  5. Enter information about your Version, then click Create.

    • General Info: Provide basic information about your API. The name is the API name plus the version number.

      • Description: Enter a brief description.

      • Version: Define the version. By default, the version is 1.0 when you create an API for the first time.

      • Tags: Enter any tags associated with your API.

    • Endpoint Configuration: The base path for the endpoint.

    • Server Configuration: Enter the Snaplex associated with this API.

    You must enter a name and Snaplex. You can also change the version from this dialog window, and therefore create another version of the API.

    After you create a version of an API, the Version asset is displayed on the Versions Details page. You can view information about the assets used in the API version by clicking it.

Creating an API Version from Existing Project Assets

  1. Navigate to API Management > API Manager, and click the target API to display the API Details page.

  2. Click the Versions tab, then click (blue star)  to display the Create Version dialog window.

  3. In the Create API version dialog window, select Create from Existing Project, then click Continue:

  4. In the Create API Version-Select Assets dialog window, select/deselect the assets from the Project to use in the API Version, then click Import and Continue.
    An Asset selected at the root level also imports the leaf-level Assets.

  5. Enter information about your API Version, then click Create.

    • General Info: Provide basic information about your API. The name is the API name plus the version number.

      • Description: Enter a brief description.

      • Version: Define the version. By default, the version is 1.0 when you create an API for the first time.

      • Tags: Enter any tags associated with your API.

    • Endpoint Configuration: The base path for the endpoint.

    • Server Configuration: Enter the Snaplex associated with this API.

    You must enter a name and Snaplex. You can also change the version from this dialog window, and therefore create another version of the API.

    After you create a version of an API, the Version asset is displayed on the Versions Details page. You can view information about the assets used in the API version by clicking it.

Creating an Empty API Version

  1. Navigate to API Management > API Manager, and click the target API to display the API Details page.

  2. Click the Versions tab, then click (blue star)  to display the Create Version dialog window.

  3. In the Create API version dialog window, select Create Empty API Version click Continue.

  4. Enter information about your Version, then click Create.

    • General Info: Provide basic information about your API. The name is the API name plus the version number.

      • Description: Enter a brief description.

      • Version: Define the version. By default, the version is 1.0 when you create an API for the first time.

      • Tags: Enter any tags associated with your API.

    • Endpoint Configuration: The base path for the endpoint.

    • Server Configuration: Enter the Snaplex associated with this API.

    You must enter a name and Snaplex. You can also change the version from this dialog window, and therefore create another version of the API.

    After you create a version of an API, the Version asset is displayed on the Versions Details page. You can view information about the assets used in the API version by clicking it.

Create the API version from a Git repository

You can create the API version from the Git repository as shown below:

  1. In the API Manager page, click on the API:

    git-op-apiversion-apimanager-accepted.png

  2. Click on the Versions tab:

    git-op-apiversion-version.png

     

  3. Click on the the add icon ( (blue star) ) and a pop-up wizard Create API version is displayed:

    git-op-apiversion-version-add.png

     

  4. In Create API version wizard, select Create from Git Checkout:

    git-op-apiversion-git-checkout.png

     

  5. Choose the Git Repository from field Repository and choose the branch from the field Branches/Tags:

    git-op-apiversion-git-repo-branch.png

     

  6. Click Continue and enter in the rest of the details, then click Create:

    git-op-apiversion-gi-details.png

     

  7. Your API version is created from Git Repository:

    git-op-apiversion-version-created.png

     

Edit API Version

You can edit the API Version with the below steps:

  1. Navigate to API Manager > API > Versions:

    version-api.png

     

  2. Click the Version you want to edit:

    versiondetails-api.png
  3. Click Edit Details to update the Version:

    editdetails-versiondetails-api.png
  4. Click Save. A message “Version details has been updated successfully” displays in the UI.

  • You can only edit the Version of the unpublished APIs.

  • Unpublish the API to edit the API Version.

  • Special characters such as |, <, >, [, ], {, },#, ?, /, and \. cannot be used.

Deleting an API version

You must delete all of the Assets in a Version before you can delete the Version.

  1. Navigate to API Management > API Manager, click the target API to display the API details page.

  2. Click the Versions tab and point your cursor on the target Version.
    The delete icon is displayed.

  3. Click (blue star)  to delete the API Version, then click Delete on the confirmation prompt.

The API Version is deleted from the API Manager console.

  • No labels