Stay organized with collections
Save and categorize content based on your preferences.
This page
applies to Apigee and Apigee hybrid.
Plugins, also known as on-ramp plugins, enable API hub to connect and ingest API metadata from various Google Cloud services and external sources where your APIs are managed or defined. They simplify and enhance the process of bringing your API metadata directly into API hub.
A plugin instance represents a configured and active connection between API hub and a specific API data source, facilitated by its associated plugin. It stores the unique configuration details required to connect to the data source, including connection credentials, curation settings, and any data import schedules. Each plugin instance serves as the entry point for collecting API metadata from its designated source.
How plugins and plugin instances work
Plugins serve as the underlying framework or capability that allows API hub to understand and integrate with different API management platforms and sources. They define how API hub can connect to a particular data source.
Plugin instances are the configured deployments of a plugin. You create a plugin instance to establish a live connection between API hub and a specific API data source. You can create multiple plugin instances for a single plugin, each with its own configuration and data curation logic.
Plugin types
The following plugin types are supported in API hub:
Built-in plugins: these are pre-built plugins developed and maintained by API hub to integrate with specific Google Cloud services and external platforms. Built-in plugins are of two types:
Google Cloud plugins: these plugins are created and maintained by API hub to integrate with specific Google Cloud services. Plugin instances of these plugins are created during the process of attaching a runtime project to API hub. For more information, see Attach a runtime project.
Non-Google Cloud plugins: these plugins are created and maintained by API hub to integrate with specific non-Google Cloud services. Plugin instances of these plugins are created from the API hub > Settings page. For more information, see Create plugin instance.
For a list of all the built-in plugins supported in API hub, see Supported plugins.
Custom plugins: these plugins are created manually to connect API hub to a specific API data source. You can create custom plugins to connect to on-premises or multi-cloud sources, or to adapt API hub to meet specific business needs.
The following data ingestion methods are available for plugins:
Push-based ingestion: the connected data source actively sends (pushes) API metadata updates to API hub as changes occur. 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 plugins are created with push-based ingestion by default.
Pull-based ingestion: API hub periodically polls the connected data source to retrieve API metadata.
[[["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-08-26 UTC."],[],[],null,["# Plugins overview\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\nPlugins, also known as *on-ramp plugins*, enable API hub to connect and ingest API metadata from various Google Cloud services and external sources where your APIs are managed or defined. They simplify and enhance the process of bringing your API metadata directly into API hub.\n\n\nA *plugin instance* represents a configured and active connection between API hub and a specific API data source, facilitated by its associated plugin. It stores the unique configuration details required to connect to the data source, including connection credentials, [curation](/apigee/docs/apihub/curations) settings, and any data import schedules. Each plugin instance serves as the entry point for collecting API metadata from its designated source.\n\nHow plugins and plugin instances work\n-------------------------------------\n\n\nPlugins serve as the underlying framework or capability that allows API hub to understand and integrate with different API management platforms and sources. They define how API hub can connect to a particular data source.\n\n\nPlugin instances are the configured deployments of a plugin. You create a plugin instance to establish a live connection between API hub and a specific API data source. You can create multiple plugin instances for a single plugin, each with its own configuration and data curation logic.\n\n### Plugin types\n\nThe following plugin types are supported in API hub:\n\n- **Built-in plugins:** these are pre-built plugins developed and maintained by API hub to integrate with specific Google Cloud services and external platforms. Built-in plugins are of two types:\n 1. **Google Cloud plugins:** these plugins are created and maintained by API hub to integrate with specific Google Cloud services. Plugin instances of these plugins are created during the process of attaching a runtime project to API hub. For more information, see [Attach a runtime project](/apigee/docs/apihub/auto-register-apigee-proxies#attach-a-runtime-project).\n 2. **Non-Google Cloud plugins:** these plugins are created and maintained by API hub to integrate with specific non-Google Cloud services. Plugin instances of these plugins are created from the **API hub \\\u003e Settings** page. For more information, see [Create plugin instance](/apigee/docs/apihub/create-plugin-instance).\n\n For a list of all the built-in plugins supported in API hub, see [Supported plugins](#supported-plugins).\n- **Custom plugins:** these plugins are created manually to connect API hub to a specific API data source. You can create custom plugins to connect to on-premises or multi-cloud sources, or to adapt API hub to meet specific business needs.\n\n\n For more information, see [Create custom plugins](/apigee/docs/apihub/create-custom-plugins).\n\nSupported plugins\n-----------------\n\nThe following table lists the plugins that are currently supported in API hub:\n\nPlugin data ingestion methods\n-----------------------------\n\nThe following data ingestion methods are available for plugins:\n| **Deprecated:** 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 and hybrid plugins configured, these plugins will continue to function and will be automatically migrated to the push-based type starting **August, 2025**.\n\n- **Push-based ingestion:** the connected data source actively sends (pushes) API metadata updates to API hub as changes occur. 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** plugins are created with push-based ingestion by default.\n- **Pull-based ingestion:** API hub periodically polls the connected data source to retrieve API metadata.\n\nWhat's next\n-----------\n\n- Learn about [creating custom plugins](/apigee/docs/apihub/create-custom-plugins).\n- Learn about [managing custom plugins](/apigee/docs/apihub/manage-custom-plugins).\n- Learn about [creating plugin instances](/apigee/docs/apihub/create-plugin-instance).\n- Learn about [managing plugin instances](/apigee/docs/apihub/manage-plugin-instances).\n- Learn about [curations](/apigee/docs/apihub/curations)."]]
