Apigee all release notes

Addendum to Apigee release notes dated August 27, 2026 (1-18-0-apigee-4).

SemanticCacheLookup policy supports non-default Vector Search distance measures

Available in Apigee 1-18-0-apigee-4 and later. A new optional <DistanceMeasureType> element accepts DOT_PRODUCT_DISTANCE (the default, and the existing behavior), COSINE_DISTANCE, SQUARED_L2_DISTANCE and L1_DISTANCE. The policy now compares <Threshold> in the direction the declared measure implies, so declaring a non-default measure requires re-tuning the threshold in the same edit. The 0-to-1 restriction on <Threshold> is also removed.

Apigee Edge for Private Cloud release notes are now published on Google Cloud documentation.

Release notes and patch announcements for Apigee Edge for Private Cloud are published on the Apigee Edge for Private Cloud release notes page from September 2026 onward. You can subscribe to that page with a feed reader to be notified when a new release or patch is published.

Release notes published before September 2026 remain available in the Apigee Edge release notes archive.

Apigee Edge for Public Cloud release notes are now published on Google Cloud documentation.

Release notes for Apigee Edge for Public Cloud, including its Edge UI, SSO, Message Processor, and integrated portal components, are published on the Apigee Edge for Public Cloud release notes page from September 2026 onward. You can subscribe to that page with a feed reader to be notified when a new release is published.

Release notes published before September 2026 remain available in the Apigee Edge release notes archive.

On September 1, 2026, we released an updated version of the Apigee UI.

On August 27th, 2026, we released an updated version of Apigee (1-18-0-apigee-4).

This list is incomplete; see entries for September 9, 2026 and September 10, 2026.

v1.14.8

On August 26, 2026 we released an updated version of the Apigee hybrid software, v1.14.8.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.14.8.
• For information on new installations, see The big picture.

On August 13th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.

If you set a preferred window for maintenance for your instance, and your instance version is below 1-18-0-apigee-2, your instance will be updated to 1-18-0-apigee-2 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.

For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.

On August 13th, 2026, we released an updated version of Apigee (1-18-0-apigee-3).

Configure and deploy MCP servers with gcloud CLI

You can use the gcloud apihub locations configure-and-deploy-server command to configure and deploy API hub Model Context Protocol (MCP) servers to an attached Apigee runtime. Define MCP tools inline or by referencing a YAML or JSON specification file to expose your API hub operations for agent integrations.

For more information, see gcloud CLI for API hub.

v1.16.9

On August 11, 2026 we released an updated version of the Apigee hybrid software, v1.16.9.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.16.9.
• For information on new installations, see The big picture.

Fixed in this release

Various security and CVE fixes are included in this release.

v1.15.7

On July 31, 2026 we released an updated version of the Apigee hybrid software, v1.15.7.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.15.7.
• For information on new installations, see The big picture.

Runtime rollout strategy configuration

In this release, you can configure the rollout strategy used when updating runtime (message processor) ReplicaSets by setting the runtime.release.strategy property (with options rolling, scale-down-first, or none) or per-environment with envs[].components.runtime.release.strategy in your overrides configuration file. The property defaults to rolling.

Various security and CVE fixes are included in this release.

On July 27th, 2026, we released an updated version of Apigee (1-18-0-apigee-2).

SanitizeUserPrompt and SanitizeModelResponse policies now support function calling

The SanitizeUserPrompt and SanitizeModelResponse policies now handle LLM function calling (tool use) flows. Two new optional XML elements extract function calling content for Model Armor sanitization:

• <FunctionResponseSource> in SanitizeUserPrompt: extracts function/tool response data from user turns. Used as a fallback when <UserPromptSource> returns empty on function calling turns.
• <FunctionCallSource> in SanitizeModelResponse: extracts function call arguments from model responses. Used as a fallback when <LLMResponseSource> returns empty.

Default templates target the Gemini format and require no additional configuration. For OpenAI and Anthropic formats, configure custom JSONPath templates. For more information, see FunctionResponseSource and FunctionCallSource.

General availability (GA) launch of Model Context Protocol (MCP) in API hub

The API hub MCP server is Generally Available (GA). This release enables seamless integration between your AI agents and API hub, allowing your applications to discover, query, and manage your API ecosystem using natural language.

What's new in GA

• Expanded read and write capabilities: AI agents can create, update, and delete APIs, versions, specs, and deployments. They can also configure and deploy MCP discovery proxies in Apigee.
• Global endpoint routing: Connect to the API hub MCP server using the global endpoint (apihub.googleapis.com/mcp), in addition to the supported regional endpoints. For a list of supported regions, see the API hub MCP reference.
• Granular OAuth scopes: Use service-specific OAuth scopes (apihub.readonly and apihub.readwrite) for more secure access.
• Model Armor integration: Protect MCP tool invocations from prompt-injection and other attacks by integrating with Model Armor.

For configuration details and a complete list of available tools, see API hub MCP reference.

Configure and deploy MCP servers with API hub RPC

API hub now includes a new RPC, ConfigureAndDeployServer, which enables the configuration and deployment of Model Context Protocol (MCP) servers directly to an Apigee runtime.

For more information, see Manage MCP proxies and the API hub reference.

v1.16.8

On July 24, 2026 we released an updated version of the Apigee hybrid software, v1.16.8.

• For information on upgrading, see Upgrading Apigee hybrid to version 1.16.
• For information on new installations, see The big picture.

Fixed in this release

Runtime rollout strategy configuration

In this release, you can configure the rollout strategy used when updating runtime (message processor) ReplicaSets by setting the runtime.release.strategy property (with options rolling, scale-down-first, or none) or per-environment with envs[].components.runtime.release.strategy in your overrides configuration file. The property defaults to rolling.

Various security and CVE fixes are included in this release.

v1.14.7

On July 23, 2026 we released an updated version of the Apigee hybrid software, v1.14.7.

• For information on upgrading, see Upgrading Apigee hybrid to version 1.14.
• For information on new installations, see The big picture.

Runtime rollout strategy configuration

In this release, you can configure the rollout strategy used when updating runtime (message processor) ReplicaSets by setting the runtime.release.strategy property (with options rolling, scale-down-first, or none) or per-environment with envs[].components.runtime.release.strategy in your overrides configuration file. The property defaults to rolling.

Various security and CVE fixes are included in this release.

On July 16, 2026, we released an updated version of the Apigee UI.

Updated PDU and basepath limits display in the Apigee UI

Removed the ambiguous org-wide PDU limit visualization from the Apigee proxy usage card. Added display of Deployments per instance and Per-org basepaths limits to the Instance details page in the Apigee UI.

On July 16th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.

If you set a preferred window for maintenance for your instance, and your instance version is below 1-17-0-apigee-10, your instance will be updated to 1-17-0-apigee-10 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.

For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.

Apigee UI

Fixed an issue where editing a legacy API Product with a selected API Proxy could cause the Apigee UI to become unresponsive.

On July 15th, 2026, we released an updated version of Apigee (1-18-0-apigee-1).

v1.15.6

On July 15, 2026 we released an updated version of the Apigee hybrid software, v1.15.6.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.15.6.
• For information on new installations, see The big picture.

Various security and CVE fixes are included in this release.

Deprecation and shutdown of GenAI Incident Summary (generative AI Insights)

The standalone GenAI Incident Summary (generative AI Insights) feature in Apigee Advanced API Security Abuse Detection, currently in Preview, is deprecated and shut down as of July 9, 2026. This feature used Google Cloud generative AI large language models (LLMs) to provide automated summaries and mitigation guidance for security incidents identified by the Abuse Detection clustering tool.

For more information, see GenAI Incident Summary deprecation.

v1.16.7

On July 10, 2026 we released an updated version of the Apigee hybrid software, v1.16.7.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.16.7.
• For information on new installations, see The big picture.

Various security and CVE fixes are included in this release.

An Improper Input Validation vulnerability in BigQuery DAO in Google Cloud Apigee versions prior to 2026-06-12 on Google Cloud Platform allowed an authenticated attacker to exfiltrate cross-tenant data.

This vulnerability was patched on 12 June 2026 on the Apigee Servers, and no customer action is needed. Apigee hybrid was not affected.

For more information, see CVE-2026-12879.

On July 6, 2026, we released an updated version of the Apigee UI.

ParsePayload policy and payload operations matching in the Apigee UI

The Apigee UI now supports the new payload operations matching feature:

• The new ParsePayload policy is now available in the proxy editor for API proxy authoring. You can use it to extract logical operations from structured payloads at runtime.
• The API Product page now displays payload-based operations, allowing you to configure and manage access control and quotas based on request payload content.

For more information, see Manage MCP tool access with API products.

Support for payload operations matching in API Products

Apigee now supports payload operations matching (payloadOperationGroup) in API Products, powered by the new ParsePayload policy.

Payload operations matching allows you to define API Product operations that match fields within request payloads, such as JSON-RPC requests used by the Model Context Protocol (MCP). Apigee can then route, monetize, authorize, and apply distinct quota limits to traffic based on the derived payload operation.

This feature is available to all Apigee X customers in all supported regions with no additional charge. For more information, see Manage MCP tool access with API products and the ParsePayload policy reference.

v1.15.5

On July 3, 2026 we released an updated version of the Apigee hybrid software, v1.15.5.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.15.5.
• For information on new installations, see The big picture.

Various security and CVE fixes are included in this release.

Apigee Emulator

Apigee Emulator v2.0.1

On June 24, 2026, we released Apigee Emulator version 2.0.1.

This is a security-only hotfix release on top of v2.0.0 that addresses 10 security vulnerabilities in the Netty networking library and the embedded Cassandra Go standard library health-check binary. There are no functional, API, or configuration changes -- v2.0.1 is a drop-in replacement for v2.0.0.

The emulator image is available at Google Artifact Registry.

To upgrade, update the emulator version in your VS Code Cloud Code settings to 2.0.1. See Manage the Apigee Emulator for details.

Apigee Emulator

Changed in this release

• Upgraded Netty to 4.1.135.Final (from 4.1.133.Final) and pinned all transitive netty-* artifacts via netty-bom.
• Refreshed the Cassandra base image to pick up Go standard library 1.25.11 (from 1.25.10) in the embedded health-check binary.
• Updated netty-tcnative-boringssl-static classifier variants from 2.0.53.Final to 2.0.77.Final.

Apigee Emulator

Security

This release addresses 10 security vulnerabilities in the Netty networking library and the embedded Go standard library. All Netty fixes come from upgrading to 4.1.135.Final; all Go standard library fixes come from a Cassandra base image rebuild against Go 1.25.11.

On June 22nd, 2026, we released an updated version of Apigee (1-17-0-apigee-10).

v1.16.6

On June 19, 2026 we released an updated version of the Apigee hybrid software, v1.16.6.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.16.6.
• For information on new installations, see The big picture.

HAProxy PROXY-protocol support on Apigee ingress gateway

In this release, you can opt into HAProxy PROXY-protocol parsing by setting the ingressGateways[].proxyProtocol.mode property (with options strict, permissive, or disable) in your overrides configuration file. The property defaults to disable.

Various security and CVE fixes are included in this release.

On June 18th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.

If you set a preferred window for maintenance for your instance, and your instance version is below 1-17-0-apigee-9, your instance will be updated to 1-17-0-apigee-9 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.

For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.

v1.14.6

On June 16, 2026 we released an updated version of the Apigee hybrid software, v1.14.6.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.14.6.
• For information on new installations, see The big picture.

Various security and CVE fixes are included in this release.

On June 8th, 2026, we released an updated version of Apigee (1-17-0-apigee-9).

v1.16.5

On June 8, 2026 we released an updated version of the Apigee hybrid software, v1.16.5.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.16.5.
• For information on new installations, see The big picture.

Various security and CVE fixes are included in this release.

On June 2nd, 2026, we released an updated version of Apigee Cassandra.

v1.15.4

On May 30, 2026 we released an updated version of the Apigee hybrid software, v1.15.4.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.15.4.
• For information on new installations, see The big picture.

Various security and CVE fixes are included in this release.

On May 29, 2026, we released an updated version of the Apigee UI.

Apigee EventFlow now supports the DataCapture policy

You can now use the DataCapture policy within an EventFlow to extract and persist data from server-sent events (SSE) streams, such as token counts and other fields from streaming LLM responses. For more information, see Use the DataCapture policy to capture token counts.

Manage Spaces in the Apigee UI

You can now create, view, update, and delete spaces, and manage their Identity and Access Management (IAM) policies directly in the Apigee UI. Previously, these actions could only be performed using the Apigee API. For more information, see Apigee Spaces overview.

Apigee Emulator

Apigee Emulator v2.0.0

On May 22, 2026, we released Apigee Emulator version 2.0.0.

Starting with this release, the Apigee Emulator is versioned and released independently from Apigee hybrid. This enables faster delivery of security patches and updates without waiting for hybrid release cycles. The emulator image continues to be available at Google Artifact Registry.

To use the new version, update the emulator version in your VS Code Cloud Code settings to 2.0.0. See Manage the Apigee Emulator for details.

Apigee Emulator

Changed in this release

• The Apigee Emulator now follows independent semantic versioning (MAJOR.MINOR.PATCH), decoupled from Apigee hybrid versioning.
• Updated base Cassandra image to version 4.0.19.
• Updated Java runtime to Eclipse Temurin JRE 11.0.31.

Apigee Emulator

Security

This release addresses 78 security vulnerabilities across Cassandra base image, Go standard library, Java dependencies, and Python packages. Key fixes include:

And 68 additional CVEs fixed through updated upstream dependencies.

v1.14.5

On May 22, 2026 we released an updated version of the Apigee hybrid software, v1.14.5.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.14.5.
• For information on new installations, see The big picture.

Various security and CVE fixes are included in this release.

On May 22, 2026 we released an updated version of the Apigee UI.

The Management > Instances page now displays Apigee hybrid instances. The display includes the instance name, location, and runtime version.

See Managing instances.

Apigee Emulator is now released independently

Starting May 22, 2026, the Apigee Emulator is versioned and released independently from Apigee hybrid. Emulator updates, including security patches, are no longer tied to hybrid release cycles.

The emulator image continues to be available at gcr.io/apigee-release/hybrid/apigee-emulator. The first independent release is v2.0.0.

For emulator release notes going forward, see Apigee release notes.

On May 21st, 2026, we released an updated version of Apigee (1-17-0-apigee-8).

v1.16.4

On May 21, 2026 we released an updated version of the Apigee hybrid software, v1.16.4.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.16.4.
• For information on new installations, see The big picture.

Fixed in this release

On May 20, 2026, we published a security bulletin for Apigee.

A vulnerability was found in Apigee (CVE-2026-2264) where the IntegrationRegion parameter in the SetIntegrationRequest policy lacks validation, allowing for Server-Side Request Forgery (SSRF) and service account token exfiltration. The issue arises when an attacker can control a flow variable used for IntegrationRegion, leading to requests being sent to an attacker-controlled host with the service account token.

Security bulletin published: GCP-2026-034

v1.16.3

On May 19, 2026 we released an updated version of the Apigee hybrid software, v1.16.3.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.16.3.
• For information on new installations, see The big picture.

Fixed in this release

Custom environment variables for Guardrail pods (guardrails.envVars)

Starting in version v1.16.3, you can inject custom environment variables into Apigee hybrid Guardrail pods using the new guardrails.envVars property in overrides.yaml. This is most commonly used to set NO_PROXY (or no_proxy) so that Guardrail pods bypass a configured forward HTTP proxy when calling internal in-cluster endpoints such as the Kubernetes API server, which previously failed in restricted-network environments with a global httpProxy configured. The property is supported on Guardrail pods for the following components: apigee-datastore, apigee-env, apigee-ingress-manager, apigee-operator, apigee-org, apigee-redis, apigee-telemetry, and apigee-virtualhost.

Example:

guardrails:
  envVars:
    NO_PROXY: 'kubernetes.default.svc,172.20.0.1'

v1.16.2

On May 13, 2026 we released an updated version of the Apigee hybrid software, v1.16.2.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.16.2.
• For information on new installations, see The big picture.

Basic Auth credential support for forward proxies

Starting in version v1.16.2, Apigee hybrid runtime components can accept credentials for an upstream forward proxy that enforces HTTP Basic Auth. You can now configure a Basic Auth username and password for the forward proxy in your overrides.yaml. This resolves known issue tracked in b/499322601. See Configure Apigee hybrid to use a forward proxy.

Sidecar authentication for Workload Identity Federation on AKS and EKS

Starting in version v1.16.2, you can now use a sidecar along with Workload Identity Federation on AKS and EKS to mount security tokens from your preferred identity provider (IDP) for service account authentication. This method is an alternative to using Kubernetes Projected Service Account Tokens, and is useful when you need to integrate with a custom Identity Provider. See Use sidecar authentication for Workload Identity Federation on AKS and EKS.

Fixed in this release

Various security and CVE fixes are included in this release.

MCP tools support for Agentic AI workflows (Preview)

API hub now exposes read-only APIs as Model Context Protocol (MCP) tools. Agentic AI applications can now use the standard MCP tools/list and tools/call methods to list and inspect API hub resources, including APIs, specs, versions, and deployments.

This feature is in Public Preview. For more information, see API hub MCP reference.

On May 12th, 2026, we released an updated version of Apigee (1-17-0-apigee-7).

Unified MCP Proxy Configuration in API hub (Preview)

API hub allows you to create and deploy Model Context Protocol (MCP) discovery proxies. Select specific API operations from your registered catalog, bundle them into an MCP server, and automatically deploy them as discovery proxies in your Apigee project. This feature eliminates the need to manually author MCP specifications in Apigee.

This feature is in Public Preview. For more information, see Manage MCP proxies.

v1.15.3

On May 4, 2026 we released an updated version of the Apigee hybrid software, v1.15.3.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.15.3.
• For information on new installations, see The big picture.

On April 29th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.

If you set a preferred window for maintenance for your instance, and your instance version is below 1-17-0-apigee-4, your instance will be updated to 1-17-0-apigee-4 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.

For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.

v1.14.4

On April 27, 2026 we released an updated version of the Apigee hybrid software, v1.14.4.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.14.4.
• For information on new installations, see The big picture.

Sidecar authentication for Workload Identity Federation on non-GKE platforms

Starting in version v1.14.4, you can now use a sidecar along with Workload Identity Federation on non-GKE platforms to mount security tokens from your preferred identity provider (IDP) for service account authentication. See Use sidecar authentication for Workload Identity Federation on non-GKE platforms.

v1.16.1

On April 20, 2026 we released an updated version of the Apigee hybrid software, v1.16.1.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.16.1.
• For information on new installations, see The big picture.

Fixed in this release

Relaxed limitation on header name for Client IP resolution

The client IP can now be resolved from any header, not just the X-Forwarded-For header. The most common headers are X-Forwarded-For or True-Client-Ip.

For more information, see Client IP resolution.

Agent Registry integration support for MCP metadata (Preview)

API hub now includes a managed integration with Agent Registry to automatically synchronize Model Context Protocol (MCP) servers and tools metadata. This feature enables AI agents to discover and interact with the APIs registered in your hub without manual configuration.

This feature is in Public Preview. For more information, see Manage Agent Registry integration.

Correction to April 2, 2026 release note: Deployment disruption for Apigee Drupal Portal via Google Cloud Marketplace

For the deployment disruption announced on April 2, the announcement noted that deployment and management functionality using Google Cloud Deployment Manager would definitely be unavailable during the transition. This statement is incorrect. The functionality might be unavailable.

See the Known issue for more information.

On April 6th, 2026, we released an updated version of Apigee.

This change introduces the new apigee.coreServiceAgent IAM role for Apigee. Effective immediately, use apigee.coreServiceAgent instead of the apigee.serviceAgent role.

For information on the new role, see apigee.coreServiceAgent.

Deployment disruption for Apigee Drupal Portal via Google Cloud Marketplace

Google Cloud Deployment Manager was deprecated as of March 31, 2026. We are currently transitioning the Apigee Drupal Portal Marketplace solution to use Infrastructure Manager. During this transition period, some deployment and management functionalities are unavailable.

Impact:

• New Deployments: Starting April 1, 2026, attempting to deploy a new Apigee Drupal Portal instance using the "Deploy" button on the Google Cloud Marketplace will fail.
• Existing Deployments: Your underlying resources (such as VMs and Cloud SQL databases) are unaffected and will continue to run normally. However, you can no longer use Deployment Manager-based features to manage the deployment via the Marketplace UI or the gcloud deployment-manager tool.

Workaround & Resolution: Any configuration changes or management tasks must be performed directly on the individual Google Cloud resources (Compute Engine, Cloud SQL, etc.) rather than through the Marketplace UI.

We are actively working to release the updated Infrastructure Manager-based solution.

On March 31st, 2026, we released an updated version of Apigee.

General Availability (GA) launch of Model Context Protocol (MCP) in Apigee

With this release, Model Context Protocol (MCP) in Apigee is generally available, enabling you to expose your Apigee APIs as MCP tools to agentic applications.

Any MCP client that supports remote MCP endpoints over HTTP/S can access these tools. Because the endpoints are managed, you don't need to install or manage local MCP servers, remote MCP servers, or additional infrastructure to enable agentic applications to access your services.

MCP in Apigee is available for Subscription, Pay-as-you-go, and Evaluation organizations, including organizations with Data Residency and VPC Service Controls enabled.

For more information on using MCP in Apigee, see MCP in Apigee overview.

Enhanced OAS server URL path handling for MCP in Apigee

With this feature enhancement, your OpenAPI specification (OAS) configurations behave exactly as defined in the OAS standard, automatically combining the server.url base path value with individual operation paths.

For example, a server URL ofhttps://example.com/api/v1 paired with a path of /users will now correctly route to https://example.com/api/v1/users without additional manual intervention.

If you previously prepended base paths to your OAS paths entries, remove the path segment from your servers.url field to prevent duplication. For example, change https://example.com/api/v1 to https://example.com.

For more information, see Create an OpenAPI 3.0 specification.

Updated MCP server target endpoint for MCP Discovery Proxies

With the GA launch of Model Context Protocol (MCP) in Apigee, the structure of the MCP server target endpoint for MCP Discover Proxies has changed to ORG_NAME.mcp.apigee.internal.

Private preview customers using the previous format (mcp.apigee.internal) are encouraged to update their proxies to reflect the new structure. Existing endpoints using the old format will continue to work, but new endpoints will use the new structure.

Known Issue 496552286: Deployment fails for MCP Discovery Proxies in regions with capacity limitations.

For more information, see Apigee known issues.

On March 26th, 2026, we released an updated version of Apigee (1-17-0-apigee-6).

On March 19th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.

If you set a preferred window for maintenance for your instance, and your instance version is below 1-16-0-apigee-6, your instance will be updated to 1-16-0-apigee-6 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.

For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.

On March 17, 2026 we released an updated version of Advanced API Security abuse detection

VPC-SC support in abuse detection

This release includes full support in Advanced API Security abuse detection for VPC-SC customers. This includes support for VPC-SC with the Advanced Anomaly Detection ML model used for abuse detection, as well as detection exclusion lists.

For usage information, see Abuse detection in the documentation.

On March 17th, 2026, we released an updated version of Apigee (1-17-0-apigee-5).

On March 13, 2026, we released an updated version of the Apigee UI.

Manage environment-scoped Key Value Maps in the Apigee UI

You can now view, add, edit, and delete environment-scoped Key Value Map (KVM) entries in the Apigee UI. For more information, see Using key value maps.

hybrid 1.16.0-hotfix.2

On March 12, 2026 we released Apigee hybrid 1.16.0-hotfix.2.

Apply this hotfix with the following steps:

Apply this hotfix with the following steps:

1. In your hybrid Helm charts directory, download the Apigee hybrid 1.16.0-hotfix.2 Helm charts into your hybrid Helm charts directory with the following commands:

   export CHART_REPO=oci://us-docker.pkg.dev/apigee-release/apigee-hybrid-helm-charts
   export CHART_VERSION=1.16.0-hotfix.2
   helm pull $CHART_REPO/apigee-operator --version $CHART_VERSION --untar
   helm pull $CHART_REPO/apigee-datastore --version $CHART_VERSION --untar
   helm pull $CHART_REPO/apigee-env --version $CHART_VERSION --untar
   helm pull $CHART_REPO/apigee-ingress-manager --version $CHART_VERSION --untar
   helm pull $CHART_REPO/apigee-org --version $CHART_VERSION --untar
   helm pull $CHART_REPO/apigee-redis --version $CHART_VERSION --untar
   helm pull $CHART_REPO/apigee-telemetry --version $CHART_VERSION --untar
   helm pull $CHART_REPO/apigee-virtualhost --version $CHART_VERSION --untar
   

2. Install the hotfix release for Apigee operators, beginning with a dry run:

   helm upgrade operator apigee-operator/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     -f overrides.yaml \
     --dry-run=server
   

3. After the dry run is successful, install the hotfix release for Apigee operators:

   helm upgrade operator apigee-operator/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     -f overrides.yaml
   

4. Install the hotfix release for your organization, beginning with a dry run:

   helm upgrade $ORG_NAME apigee-org/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     -f overrides.yaml \
     --dry-run=server
   

5. After the dry run is successful, install the hotfix release for your organization:

   helm upgrade $ORG_NAME apigee-org/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     -f overrides.yaml
   

6. Verify the organization chart by checking the state:

   kubectl -n APIGEE_NAMESPACE get apigeeorg
   

7. Install the hotfix release for your environments. Repeat the following steps for each environment, beginning with a dry run:

   helm upgrade ENV_RELEASE_NAME apigee-env/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     --set env=$ENV_NAME \
     -f overrides.yaml \
     --dry-run=server
   

8. After the dry run is successful, install the hotfix release for your environment:

   helm upgrade ENV_RELEASE_NAME apigee-env/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     --set env=$ENV_NAME \
     -f overrides.yaml
   

9. Verify the environment chart by checking the state:

   kubectl -n APIGEE_NAMESPACE get apigeeenv
   

Fixed in this release

hybrid v1.15.2

On March 11, 2026 we released an updated version of the Apigee hybrid software, v1.15.2.

• For information on upgrading, see Upgrading Apigee hybrid to version v1.15.2.
• For information on new installations, see The big picture.

Fixed in this release

Security monitoring condition support in Advanced API Security for multi-gateway projects

Advanced API Security's multi-gateway Risk Assessment feature (available through API hub) now includes support for security monitoring conditions and alerts.

Security monitoring conditions allow you to map resources (gateways) to security profiles. Cloud Monitoring can then use this mapping to create dedicated dashboards to track security scores over time and alert based on metric levels.

For information on monitoring conditions features and usage see Manage monitoring conditions for multiple Apigee organizations and gateways.

Support for Apigee Edge Private Cloud (OPDK) in Advanced API Security for multi-gateway projects

API hub Advanced API Security for multi-gateway now includes support for the OPDK gateway type for risk assessment security profiles.

For information on risk assessment custom security profiles and gateway specification, see Create a security profile.

On March 10, 2026 we released an updated version of Advanced API Security Abuse Detection

General availability of monitoring conditions in risk assessment v2

Starting with this release, the risk assessment v2 monitoring conditions feature is generally available.

For information on monitoring conditions features and usage see monitoring conditions and alerts. For usage information and a list of all features in Risk Assessment v2, see the Risk Assessment v2 customer documentation.

On March 10th, 2026, we released an updated version of Apigee (1-17-0-apigee-4).

On March 5, 2026 we released a new version of the Apigee integrated portal.

You can now publish APIs using AsyncAPI documents to render documentation for asynchronous APIs in your portal. For more information, see Publishing your APIs.

gcloud CLI support for API hub

The gcloud CLI now supports Apigee API hub, allowing you to manage your organization's API catalog, versions, and lifecycle metadata directly from the command line.

For more information see gcloud CLI for API hub.

On February 24th, 2026, we released an updated version of Apigee (1-17-0-apigee-3).

Preview release of specification boost

API hub now supports the preview release of specification boost, an AI-powered add-on that lets you automatically enhance the readability and discoverability of your API specifications in API hub. It analyzes your existing specification files and generates boosted versions enriched with richer details, including additional examples, clearer descriptions, better error documentation, and more.

For more information see Specification boost add-on.

On February 13, 2026, we released an updated version of the Apigee UI.

Updated the route for Operations Anomalies from apigee/analytics/operations-anomalies to apigee/aapi-ops/operations-anomalies.

On February 13, 2026, we published a security bulletin for Apigee.

A vulnerability was identified in the Apigee platform (CVE-2025-13292) that could have allowed a malicious actor with administrative or developer-level permissions in their own Apigee environment to elevate privileges and access cross-tenant data.

Security bulletin published: GCP-2026-010

On February 10, 2026, we released an updated version of Apigee (1-17-0-apigee-2).

On February 6th, 2026, we released an updated version of Apigee.

hybrid 1.16.0-hotfix.1

On February 6, 2026 we released Apigee hybrid 1.16.0-hotfix.1.

Apply this hotfix with the following steps:

1. In your overrides file, update the image.url and image.tag properties of ao and mart to version 1.16.0-hotfix.1:

   ao:
     image:
       url: "gcr.io/apigee-release/hybrid/apigee-operators"
       tag: "1.16.0-hotfix.1"
   mart:
     image:
       url: "gcr.io/apigee-release/hybrid/apigee-mart-server"
       tag: "1.16.0-hotfix.1"
   

2. Install the hotfix release for Apigee operators, beginning with a dry run:

   helm upgrade operator apigee-operator/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     -f overrides.yaml \
     --dry-run=server
   

3. If the dry run is successful, install the hotfix release for Apigee operators:

   helm upgrade operator apigee-operator/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     -f overrides.yaml
   

4. Install the hotfix release for your organization, beginning with a dry run:

   helm upgrade $ORG_NAME apigee-org/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     -f overrides.yaml \
     --dry-run=server
   

5. If the dry run is successful, install the hotfix release for your organization:

   helm upgrade $ORG_NAME apigee-org/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     -f overrides.yaml
   

6. Verify the organization chart by checking the state:

   kubectl -n APIGEE_NAMESPACE get apigeeorg
   

7. Install the hotfix release for your environment, beginning with a dry run:

   helm upgrade ENV_RELEASE_NAME apigee-env/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     --set env=$ENV_NAME \
     -f overrides.yaml \
     --dry-run=server
   

8. If the dry run is successful, install the hotfix release for your environment:

   helm upgrade ENV_RELEASE_NAME apigee-env/ \
     --install \
     --namespace APIGEE_NAMESPACE \
     --atomic \
     --set env=$ENV_NAME \
     -f overrides.yaml
   

9. Verify the environment chart by checking the state:

   kubectl -n APIGEE_NAMESPACE get apigeeenv
   

Fixed in this release

On February 3, 2026 we released an updated version of Advanced API Security security actions

Support for configuring two condition types within a single security action Announcing the availability of support for two condition types in a single security action. For example, you can include both IP addresses and ASN numbers in the same security action.

This feature is available in Apigee and Apigee hybrid 1.16.0 and later.

Note: This feature is available when configuring the security action via the API, not the UI, at this time.

For usage information, see Configure multiple condition types in the documentation.

Known Issue: 480997525 - Proxy calls fail with The URI contains illegal characters error after Netty upgrade

On January 27, 2026, we released an updated version of the Apigee UI.

Show all rows in the Debug properties panel

Fixed an issue where only the first 50 rows were displayed in the Debug properties panel, including the variables tab. The Debug properties table now displays up to 200 rows per page by default. Pagination controls are displayed if the total number of rows exceeds 200.

On January 21st, 2026, we released an updated version of Apigee (1-17-0-apigee-1).

Debug v1 turndown

As of January 20, 2026, Debug v1 has been turned down and is no longer available. Please use Debug v2 (now referred to as Debug) for debugging API proxies.

Ingest API Gateway metadata into API hub

API hub now supports automatic metadata ingestion from Google Cloud API Gateway. You can now attach your API Gateway projects to API hub to enable auto-ingestion for all your APIs. For more information see Centralize API management using API hub.

On January 12, 2026 we released an updated version of Advanced API Security Abuse Detection

Introduction of Terraform support for managing Advanced API Security abuse detection exclusion lists

You can now use Terraform to manage Advanced API Security abuse detection exclusion lists. The feedback feature allows you to specify CIDR ranges and IP addresses to exclude from future incident reports, and is used to exclude traffic known to be safe, such as requests related to automated testing.

Note: Exclusion lists are not available for VPC-SC customers at this time.

For usage information, see Exclude traffic from abuse detection and Use Terraform in Apigee in the Apigee documentation and the Terraform abuse detection feedback (exclusion lists) instructions.

On January 12, 2026, we released an updated version of the Apigee UI.

Manage environment-level resources in the Apigee UI

You can now manage environment-level resources using the Apigee UI. Previously, environment-level resources could only be managed using the API. For more information, see Managing resources.

On January 7, 2026, we released an updated version of Apigee.

The Apigee Operator for Kubernetes version 1.1.1 is now available.

On December 29th, 2025, we released an updated version of Apigee.

The Apigee Extension Processor provisioning API is available

Apigee Extension Processor customers can now use the Extension Processor provisioning API to create traffic extensions. For more information, see Get started with the Apigee Extension Processor

On December 23, 2025, we released an updated version of Apigee.

New Apigee policies for LLM Token Management are now Generally Available (GA)

Two new Apigee policies for managing Large Language Model (LLM) workloads are now Generally Available (GA). These policies provide fine-grained control and rate-limiting for AI application traffic as follows:

• LLMTokenQuota policy
  • This policy monitors and enforces limits on LLM response token usage to control overall LLM expenditure and resource allocation.
  • It can be configured with <CountOnly> (placed in the response flow to track tokens consumed) or <EnforceOnly> (placed in the request flow to block calls if the quota is exceeded).
  • If the quota is reached, Apigee returns an HTTP 429 (Too Many Requests) status code.
  • For more information, see LLMTokenQuota Policy.
• PromptTokenLimit policy
  • This policy provides a token-based rate-limiting mechanism analogous to the SpikeArrest policy, specifically for the tokens consumed by the user's prompt message.
  • It calculates the prompt's token count using the widely adopted o200k_base encoding technique.
  • If the configured token rate limit is exceeded, the incoming request is blocked, returning an HTTP 429 (Too Many Requests) status code.
  • For more information, see PromptTokenLimit policy.

Related documents:

• Get started with Apigee AI token policies
• Rate-limiting
• Comparing rate-limiting policies
• Managing API products
• LLMTokenQuota policy
• PromptTokenLimit policy

On December 19, 2025, we released an updated version of Apigee Monetization.

Monetization now supports AppGroups. Use AppGroups to manage API product subscriptions for all app developers in the AppGroup at the same time.

For more information, see Use AppGroups to manage API product subscriptions.