API Ops Major Release 2026.1.0

May 07, 2026

In this release:

Key Features: 2026.1.0

Akana API Ops Command Line Tool introduces automation capabilities for promoting Akana API gateway and developer portal configurations across environments. This tool enables teams to replicate and promote API-related assets between environments such as development, testing, staging, and production in a consistent and repeatable manner.

Designed to support modern API operations and DevOps workflows, the tool can be executed directly from a command line or integrated into existing CI/CD pipelines to automate API promotion during deployment processes.

Key Capabilities:

  • Environment Promotion - The tool enables promotion of API gateway configurations from one environment to another, ensuring consistent configuration across environments.

  • Supported assets for promotion - The tool will allow to export or import latest version of following assets in this release. More assets and additional versions will be supported in subsequent releases

    • REST API configurations including basic fields, avatar image, specifications, documentations, licenses, scopes, OAuth settings, Outbound Identity, PKI keys & certs, header propagation settings, physical service client timeout, all types of contracts

    • Apps configuration including basic fields, oauth profile, certificates

    • Scope and Licenses

    • Standard and Custom policies used with REST APIs

    • Users

  • CI/CD Pipeline Integration - The tool is designed to integrate easily with common CI/CD platforms, enabling automated API promotion as part of deployment workflows.

  • Interpolation support for environment specific configurations - The tool provides interpolation capabilities that allow dynamic modification of configuration values during promotion. This ensures that environment-specific settings can be automatically adjusted without requiring manual change.

  • Import Strategy - The tool supports flexible import strategies create, createOrUpdate to control how assets are created or updated in the target environment.

    • Create strategy - Imports assets only if they do not already exist in the target environment

    • CreateOrUpdate strategy - Creates new assets if they do not exist and updates existing assets if already present

  • Sensitive data encryption - The tool allows to encrypt sensitive information used for the tool

  • Export & Import Tool Usage Logs (Observability) - The tool includes logging and observability capabilities for export and import operations, enabling teams to track and analyze API promotion activities.

    • Export and Import execution logs are generated in JSON format. These logs capture information about who executed which API ops commands on which assets and its status

    • Trace Logs - Tool trace logs for troubleshooting any issues.

  • CLI-Based Interface - The API Ops tool runs as an independent command line utility, allowing operators and DevOps engineers to execute promotion commands directly from terminal environments.

Benefits

  • Enables API infrastructure as code practices and reduces manual configuration errors

  • Supports DevOps and GitOps deployment models simplifying API lifecycle management

  • Ensures consistent API configuration across environments

  • Supports environment-specific customization through interpolations

Getting Started

The API Ops Command Line Tool can be downloaded from the Support Portal. Once downloaded, the tool can be installed and executed on systems that have network access to the Akana Community Manager portal. Refer the Getting Started section in the Akana API Ops documentation for instructions on how to begin using the tool.

Case number: 01351753

Known Issues: 2026.1.0

Here are some limitations associated with the API ops:

  • If the Publish in API Documentation option is not selected for an API in the source environment, the API Ops tool fails to import the exported API. Ensure that the Publish in API Documentation checkbox is selected before exporting the API.

  • The API Ops tool does not support exporting or importing Audit Logging settings when the logging level is set to Error or Warning. As a result, these configurations are not preserved during API Ops execution.

  • When importing an API into a child organization using the createOrUpdate strategy, the import fails if an API with the same name already exists at the tenant org level.

  • When the deployment zone names differ between the source and target environments, the context path does not remain consistent after the API import.

  • Custom Vanity Host (CNAME) value for a deployment zone in the source environment is not retained when the API is imported into the target environment.