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.
]]>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.
]]>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.
]]>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.
]]>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.
]]>Advanced API Security for multi-gateway projects
Apigee Advanced API Security can now centrally manage and govern the security posture of your APIs across multiple Apigee projects, environments, and gateways. This enhancement leverages API hub to provide a single, unified view of your API security, helping you to identify risks and enforce standards consistently across your entire organization.
This enhancement introduces the following key capabilities:
Supported gateways:
To enable this feature, navigate to the Add-on management page in API hub and enable the Apigee Advanced API Security add-on.
Advanced API Security currently has limited support for VPC Service Controls (VPC-SC). To avoid potential feature limitations, we recommend enabling this add-on for API hub instances associated with Apigee organizations that don't have VPC-SC enabled.
For more information, see Advanced API Security for multiple Apigee organizations and gateways.
]]>New API card view
A new card view is now available for APIs in API hub. This view provides a more visual and comprehensive way to browse, edit, and manage your APIs, complementing the existing list view.
The card view highlights key information for each API, such as the owner, last modified date, target users, gateway, API style, and business unit, to enhance discoverability and provide a richer at-a-glance overview of your API landscape.
You can switch between the list and card views from the API hub > APIs page.
]]>Model Context Protocol (MCP) support in API hub
API hub now supports the Model Context Protocol (MCP) as a first-class API style. This enables you to ingest, register, and manage MCP APIs and their associated tools.
Key capabilities include:
For more information, see API resources overview, Register MCP APIs, and Manage MCP tools.
]]>New add-on management page in API hub
A new Add-on Management page is now available in API hub. This page serves as a centralized location to enable, configure, and manage all your add-on services.
For more information, see Manage add-ons.
Actions tab changes
The Actions tab previously located in the API hub > Settings page is now removed, accounting for the following UI changes:
New API deployments view
API deployment information is now available as a separate tab in the API details page. You can view your API deployment details, create new deployments, and manage existing deployments using the API deployments tab.
For more information, see Manage deployments.
The issue relating to API hub provisioning failures in data residency enabled Apigee organizations is now resolved. You can now provision API hub within an Apigee organization that has data residency enabled.
For information about provisioning API hub, see Provision API hub in the Cloud console.
New tutorial: Ingest Microsoft Azure API data into API hub
A new tutorial is available for ingesting Microsoft Azure API data into API hub.
This tutorial shows you how to ingest API metadata from Azure API Management (APIM) into Apigee API hub. It uses a pre-built Application Integration template and a set of custom scripts on GitHub to perform a manual, on-demand ingestion of your API data.
For more information, see Ingest Microsoft Azure API data into API hub.
]]>Filter APIs by user-defined attributes
You can now filter APIs using your custom, user-defined attributes from the APIs page in the Google Cloud console.
For more information, see Filter resources based on attributes.
]]>API hub provisioning fails in data residency enabled Apigee organizations
Currently, API hub can't be provisioned within an Apigee organization that has data residency enabled. Attempts to provision API hub in a data residency-enabled Apigee organization will result in a timeout error.
Workaround: There is no workaround available at this time. If your existing Apigee organization has data residency enabled, you will not be able to provision API hub until this limitation is resolved in a future release.
]]>Detailed API resource insights
A new Insights tab is now available on the API details page, providing API-centric analytics to help you understand usage patterns and performance for each of your APIs.
You can now analyze key metrics such as total traffic, average TPS, request/response latencies, and more, directly from the API details page.
For more information, see View API resource insights.
API insights in API hub
API insights is now available in API hub, providing a unified view of your API traffic and performance across all connected gateways. With API insights, you can gain a holistic understanding of your API ecosystem's health and quickly identify areas for optimization.
Currently, API insights supports data sources from Apigee, Apigee hybrid, Apigee Edge Public Cloud, and Apigee Edge Private Cloud (OPDK).
For more information, see API insights overview.
]]>Create and manage API operations in the UI
You can now create and manage API operations for your API versions from the API details page in the Google Cloud console.
For more information, see Manage operations.
]]>New MCP API style system attribute
The system-defined API style attribute now includes a new value: MCP. This lets you classify and govern APIs based on the latest Model Context Protocol (MCP) standards.
For more information, see System attributes.
]]>API hub navigation update
The API hub section is now moved to the top level of the Apigee left navigation menu. This change improves discoverability and access to the API hub features.
Updated Go client library. For more information, see apihub: v0.2.0.
]]>Enable and disable semantic search
You can now enable and disable semantic search from the API hub > Settings> Actions page in the Google Cloud console.
For more information, see Enable and disable semantic search.
Deprecation of Vertex AI Extensions in API hub
The Vertex AI Extensions feature is no longer supported in API hub as of September 8, 2025.
Automatic discovery of OpenAPI Spec from Apigee proxy resources
API hub now automatically discovers and ingests valid OpenAPI specifications when they are included in an Apigee API proxy resource. This applies to all new and existing Apigee and Apigee hybrid runtime projects that are attached in API hub.
For more information, see Auto-discovery of OpenAPI specs from Apigee proxies.
]]>New API versions view
API version information is now available as a separate tab in the API details page. You can view your API version details, copy API ID, create new API versions and more using the API versions tab.
For more information, see Manage versions.
]]>Deprovision API hub in the UI
You can now deprovision an API hub instance from the API hub > Settings > Actions page in the Google Cloud console.
For more information, see Deprovision Apigee API hub.
Create and delete custom plugins in the UI
You can now create and delete custom plugins from the API hub > Settings > Plugins page in the Google Cloud console.
For more information, see Create custom plugins and Manage custom plugins.
]]>API observations in API hub (Preview)
API observations in API hub helps you tackle the challenges of undocumented and unmanaged APIs in your API infrastructure. It leverages Apigee shadow API discovery and uses automated discovery processes to bring all your APIs, across Google Cloud projects, into a unified, managed view.
For more information, see API observations in API hub.
]]>New data source support for plugins
API hub now supports importing API metadata through new dedicated plugins for the following data sources:
For more information, see Plugins overview.
Create custom plugins [API only]
You can now use the Create Plugin API to create custom plugins in API hub. Custom plugins are created manually to connect API hub to a specific API data source.
For more information, see Create custom plugins.
Push-based plugin ingestion
API hub now supports push-based plugin ingestion. This method allows for more real-time synchronization of API metadata. All new Apigee, Apigee hybrid, Apigee Edge Public Cloud, and Apigee Edge Private Cloud (OPDK) plugins are created with push-based ingestion by default.
For more information, see Plugin data ingestion methods.
Default Apigee plugin instance not auto-created during runtime attachment
Issue: When provisioning API hub as part of Apigee provisioning, the default Apigee X and hybrid plugin instance is not automatically created. This prevents API proxies from being auto-registered.
Workaround: You can manually attach an Apigee runtime instance and import the Apigee assets. See Attach a runtime project.
New tutorial: Enrich API data in API hub
A new tutorial is available for enriching API data in Apigee API hub.
It shows you how to use API hub's custom curation features to automatically fetch OpenAPI specifications from a Cloud Storage bucket and associate them with their corresponding Apigee API proxies. The custom curation logic is defined using an integration in Application Integration.
For more information, see Enrich API data with custom curation in API hub.
Provisioning changes and Apigee API proxy registration
API hub changed how it registers API proxies from Apigee and how it creates default plugin instances during provisioning.
API hub now automatically creates a default Apigee X and hybrid plugin instance and auto-registers API proxies only when you provision it as part of Apigee provisioning.
If you provision API hub directly from the API hub UI, API hub does not automatically create a default plugin instance, nor does it auto-register proxies.
For more information, see Project attachments and plugins.
Delete plugin instance changes
API hub no longer retains any ingested metadata from a plugin after its deletion. Deleting a plugin instance also permanently deletes all the associated API data from API hub.
For more information, see Delete a plugin instance.
Deprecation of pull-based ingestion for Apigee plugins
Pull-based ingestion is no longer supported for Apigee and Apigee hybrid plugins as of July 31, 2025. For existing projects that have pull-based Apigee X and hybrid plugins configured, these plugins will continue to function and will be automatically migrated to the push-based type starting August 2025.
Deprecation of Apigee proxy deployment attributes
As of July 31st, 2025, the Apigee X and Hybrid Environment and Apigee X and Hybrid Organization attributes will no longer be added to new Apigee proxy deployments. This change specifically applies when you import deployments into API hub by attaching a runtime project.
If your existing projects use these attributes in filtered search queries, we recommend updating them. To ensure your searches continue to work, use the Source project and Source environment fields as alternatives.
API hub deprovisioning changes
Deprovisioning an API hub instance now also deletes any associated Apigee organizations from your Google Cloud project, provided those Apigee organizations have no Apigee instances.
If you deprovision an API hub instance, you can reprovision it later, but you'll need to wait 7 days before you can do so.
For more information, see Deprovision Apigee API hub.
VPC Service Controls (VPC-SC) is GA
VPC Service Controls in API hub is now GA.
For more information, see VPC Service Controls for API hub.
API hub provisioning now enables Apigee API
When you provision API hub, it now enables the Apigee API (apigee.googleapis.com) in your Google Cloud project. If Apigee isn't already provisioned, an Apigee organization is also automatically created in your project as part of the provisioning process.
API hub remains a free service. Enabling the Apigee API has no additional pricing or billing implications for your project.
For more information, see Provision API hub in the Cloud console.
]]>Apigee and hybrid plugin instance management
You can now create and delete plugin instances for Apigee and Apigee Hybrid while associating the respective Apigee runtime projects to API hub.
For more information, see Auto-register Apigee proxies.
Apigee and Apigee hybrid plugin creation now requires source project ID
When creating new instances of the Apigee X and hybrid plugin, you must now provide a source project ID. This source project ID is the Google Cloud project from which the plugin will import data.
This is a breaking change and will affect any existing API calls that create these plugins without explicitly providing this ID.
Action Required: Update your API calls to include the appropriate source project ID when creating new Apigee X and hybrid plugins. Failing to do so will result in creation errors.
Edit plugin instances changes
You can now change or modify the name and curation logic of your plugin instance.
For more information, see Edit a plugin instance.
Resource URI format for Apigee deployments
To ensure optimal functionality and consistency while creating or updating Apigee deployments, we now recommend that the Resource URI conforms to the following format:
organizations/([^/]+)/environments/([^/]+)/apis/([^/]+)$
For more information, see Introduction to deployments.
]]>Apigee API hub is enabled for new Apigee organizations in supported regions.
With this release, we are enabling Apigee API hub for new Apigee organizations in regions where API hub is supported. All new Apigee organizations, including hybrid organizations, that select an API hub-supported region for their Apigee Analytics region during provisioning will have access to API hub features at no additional cost.
API hub allows you to view, organize, and manage all of the APIs in your Apigee organization in one central location. To learn more, see What is Apigee API hub?
No action on your part is required to provision API hub for your organization, with the following exceptions:
Contact Google Cloud Support for questions or assistance.
On June 3, 2025, we released an updated version of Apigee.
]]>Apigee API hub is now available in the following regions:
For more information, see API hub locations.
]]>API overview and metrics
The Get Started with API hub page now includes new charts and scorecards to provide a quick overview of your API landscape.
For more information see Get started with API hub.
Attach and manage Tags
You can now add custom tags to your APIs and API deployments, making it easier to organize, categorize, and discover your API resources in API hub. Tags can also be used to conditionally allow or deny policies to a specific resource.
For more information see Attach and manage tags.
Updated UI for API hub
The API hub user interface is now updated to Google Material Design 2. This update provides a more consistent and modern look and feel, enhancing the overall user experience and aligning the UI with other Google Cloud products.
]]>On April 29, 2025, we released an updated version of Apigee.
Apigee API hub is enabled for existing Apigee organizations in supported regions.
With this release, we are enabling Apigee API hub for existing Apigee organizations in regions where API hub is supported. All existing Apigee organizations, including hybrid organizations, that selected an API hub-supported region for their Apigee Analytics region will have access to API hub features at no additional cost.
API hub allows you to view, organize, and manage all of the APIs in your Apigee organization in one central location. To learn more, see What is Apigee API hub?
The process of enabling API hub for these organizations will continue over the next several weeks until all eligible organizations are updated. No action on your part is required to provision API hub for your organization, with the following exceptions:
Contact Google Cloud Support for questions or assistance.
]]>Data residency zone compliance
API hub is now compliant with data residency Zone C3 requirements.
For more information, see API hub and data residency.
VPC Service Controls (VPC-SC) integration (Preview)
API hub now integrates with VPC Service Controls, providing enhanced network security for your API hub instance provisioned in Google Cloud. Establish service perimeters to control ingress and egress traffic. For more information, see VPC Service Controls for API hub.
Terraform support for provisioning
You can now provision API hub instances programmatically using Terraform for Google Cloud within Cloud Shell, enabling infrastructure-as-code practices. For more information, see Provision API hub using Terraform.
Plugin Framework
API hub now uses a plugin framework to connect and ingest API metadata from various Google Cloud services and external sources where your APIs are managed or defined. This provides a flexible and extensible way to integrate with your existing API landscape. For more information, see Plugins overview.
Enhancements to the Operations entity [API only]
You can now add, edit, or delete operations for an API version even if it lacks a specification file or has an unparsable one. For more information, see Manage operations.
API Metadata Curations
API hub introduces a curation process to transform and enrich API metadata ingested by plugins. This ensures consistency across different sources, enabling effective governance, discovery, and management of your APIs. For more information, see Curations overview.
API Supply chain graph view
Visualize and understand the dependencies within your API ecosystem with the new interactive API supply chain graph view. This directed graph allows you to explore the relationships between your APIs and API operations. For more information, see API Supply chain views.
Deprovision an API hub instance [API only]
You can now delete an API hub instance from your Google Cloud project using the ApiHubInstance API. For more information, see Deprovision Apigee API hub.
Attach API documents
You can now enhance your API documentation by attaching additional relevant files, such as requirements, design documents, and functionality details, directly to your APIs in API hub.
]]>IAM conditions for fine-grained access
API hub now integrates with IAM Conditions, enabling you to define and enforce granular, conditional attribute-based access control for your API hub resources. For more information, see Add IAM conditions.
Enhanced onboarding experience
After provisioning your API hub instance in your Google Cloud project, you'll now see an updated Overview page. You can also automatically attach your Apigee runtime projects right from this page. For more information, see Provision API hub in the Cloud console.
Auth support for Vertex AI extensions
API hub now supports the following authentication configurations for creating Vertex AI extensions:
API Key: Authenticate using API keys stored in Secret Manager.HTTP Basic: Authenticate using credentials stored in Secret Manager.For more information, see Create a Vertex AI extension.
Resource ID length limits increased
The maximum allowed length for API hub resource IDs has been increased. The new limits are as follows:
Resource filtering with user-Defined attributes
You can now filter API hub resources based on user-defined attributes using a REST API call. For more information, see Filter resources based on user attributes.
Validation for user-defined attributes
API hub now supports JSON schema validation for user-defined attributes. This enhancement ensures data integrity and consistency for JSON data type inputs, improving the quality and reliability of API specifications.
]]>