This page documents production updates to API hub software in 2024 and later. We recommend that users periodically check this list for any new announcements, or subscribe to this page using a feed reader to get notifications of updates.
What is a feed reader?
Really simple syndication (RSS) feed readers aggregate content from websites that you specify.
Feed reader notifications can be email-, browser-, desktop-, or mobile-based. Some readers are free, or have free versions, and some require a subscription.
A few examples:
More information on RSS:
You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.
February 11, 2025
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:
- APIs: API unique IDs can now be up to 500 characters long.
- Versions: Version unique IDs can now be up to 700 characters long.
- Specs: Specification unique IDs can now be up to 1000 characters long.
January 15, 2025
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.
October 18, 2024
On October 18, 2024, Apigee announced the an update to Apigee API hub.
In addition to us-central1 and europe-west1, Apigee API hub now supports the following new hosting regions:
| Region Description | Region name |
|---|---|
| Northern Virginia | us-east4 |
| Oregon | us-west1 |
| London | europe-west2 |
| Singapore | asia-southeast1 |
| Mumbai | asia-south |
| Sao Paulo | southamerica-east1 |
| Sydney | australia-southeast1 |
See Provision API hub.
September 26, 2024
On September 26, 2024, Apigee announced the GA launch of Apigee API hub.
A new "Get started with API hub" page was added to the user interface. This new page includes valuable getting started information, including a new FAQ, to help you get the most out of API hub.
We added a new Supply chain page where you can create, view and manage your dependencies across API operations. The same dependencies can also be created from the API operations page. See Manage dependencies.
The Semantic Search (formerly Smart Search) user interface has been improved, and search results are shown across all API hub entities, such as APIs, deployments, specifications, and versions. See Search and filter APIs.
We added support for GMEK and CMEK in the provisioning steps. While provisioning, you can also choose to host your Vertex search data in a different location or disable Vertex search altogether. See Provision API hub.
We added support for Cloud audit logging.
The List APIs for specifications, dependencies, and external APIs have been enhanced to return a complete response, including user-defined attributes.
While you can use API hub by making direct REST over HTTP requests, we now provide client libraries for several popular languages. See API hub client libraries.
Significant user interface improvements were made, such as standardization of cards on the API details page, unlinking of deployments, various performance fixes, and more.
August 23, 2024
On August 23, 2024, we updated the Preview release of Apigee API hub.
You can now edit an uploaded API specification's metadata through the Cloud console. See Edit specification metadata.
You can now choose in the Cloud console to restrict the upload of an API specification file that contains errors. By default, specs containing errors are uploaded. See Add a spec to an existing version.
When an Apigee API proxy is auto-registered, its deployment type is now labeled either Apigee X or Apigee hybrid. Existing Apigee proxy deployments registered with API hub will also be labeled with the appropriate type. See Auto-register Apigee proxies.
All API proxy endpoints auto-registered from Apigee will be prefixed with https:// by default. Endpoints for existing API proxies that were added to API hub will be updated.
A validation check has been added to reject an API specification style guide upload if the style guide's extends property contains a URL. See Upload a new style guide.
User interface and performance improvements were made.
Provisioning improvements were made to address potential failures.
June 11, 2024
Vertex AI extensions
You can create Vertex AI extensions for the APIs registered in API hub. These extensions can be integrated with Large Language Models (LLMs) to process real-time data. For more information, see Create a Vertex AI extension.
Eventarc triggers
API hub is integrated with Google Cloud's Eventarc. You can now create Eventarc triggers to listen for specific events in API hub, and then trigger custom workflows based on the event. For more information, see Create an Eventarc trigger.
Multi-level delete
By default, you can delete an API only if all underlying versions are deleted. Starting with this release, you can use the force option to delete an API and its child resources in a single step. For more information, see Delete an API resource.
May 06, 2024
Apigee API hub is available in preview.
With Apigee API hub, you can consolidate and organize critical information about your APIs in one place. Use API hub to accelerate the consistency, use, reuse, and governance of your API portfolio.
Use API hub to:
- Create and manage a complete catalog of your APIs and API resources.
- Add rich attributes to your APIs for tracking, organizing, and filtering.
- Link to one or more Apigee projects to automatically fetch and store Apigee API proxy information.
- Find APIs with powerful free-form semantic search capabilities.
- Track compliance for your API specification files using Linting functionality.
To learn more about the features and functionality available, see What is Apigee API hub?
NOTE: Rollouts of this feature will begin on May 6, 2024, and may take four or more business days to be completed across all Google Cloud zones. You may not be able to provision API hub until the rollout is complete.