Stay organized with collections
Save and categorize content based on your preferences.
This page
applies to Apigee and Apigee hybrid.
You can register deployed proxies present in your Apigee
and Apigee hybrid runtime projects directly in API hub with the click of a button.
Figure 1. Auto-register APIs from Apigee and Apigee hybrid.
The proxies will be registered as API resources in API hub. To register the proxies, you must attach your runtime project to
API hub. When you attach a project, API hub registers the following information for each
proxy definition:
Name
Revision
Environment and deployment details
Type of Apigee instance (either Apigee X or Apigee hybrid)
API hub periodically (once in six hours) runs a scheduler that connects to your
Apigee project, and gets the latest proxy definitions. For the projects that are newly
attached, the scheduler gets all the proxy definitions, and then registers them in API hub.
And for the existing projects, the scheduler gets only the changes made to the proxy
definitions, and then accordingly updates the proxy information in API hub.
Attach a runtime project
To attach an Apigee runtime project to API hub, do the following steps:
In the Google Cloud console, go to the API hub > Settings > Project associations page.
Click Attach runtime project. This displays the Select a resource pane.
Click the Google Cloud project where Apigee is installed. If there aren't any errors, the project gets attached to API hub, and
will be listed in the Project associations page. However, the actual process of
registering the proxies will start after the next run of the scheduler.
Detach a runtime project
If you detach a runtime project, API hub removes all the APIs registered for that project.
To detach an Apigee runtime project from API hub, do the following steps:
In the Google Cloud console, go to the API hub > Settings > Project associations page.
Click Detach project for the project you want to detach.
Considerations
Consider the following when attempting to auto-register APIs:
All endpoints imported from Apigee will be given an https:// prefix by default.
Proxies that aren't deployed in any environment, aren't fetched from the project.
Only proxies that are deployed in an environment are fetched. And the environment must be a part
of an environment group.
API hub doesn't support VPC Service Controls. Hence, if you have enabled VPC Service Control for your Apigee runtime project,
API hub can't access the project.
If the Apigee API isn't enabled for a runtime project, API hub can't access the project.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-10 UTC."],[[["API proxies from Apigee and Apigee hybrid can be automatically registered in API hub by attaching the respective runtime project."],["API hub's scheduler periodically retrieves and registers new or updated proxy definitions from attached Apigee projects, running once every six hours."],["Attaching a runtime project to API hub requires selecting the Google Cloud project where Apigee is installed in the \"Project associations\" page."],["Detaching a runtime project from API hub removes all registered APIs associated with that project, though created attributes are retained."],["Only proxies deployed in environments that are part of an environment group are fetched, and VPC Service Controls is not supported by API hub."]]],[]]
