--- sourceDocument: Brazil ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Apigee Edge # API Service Graph Connector for Apigee Edge {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of API Service Graph Connector for Apigee Edge The ServiceNow® API Service Graph Connector for Apigee Edge enables customers to import and maintain detailed API information from Apigee Edge applications into the Configuration Management Database (CMDB). This integration supports a normalized data model, enhancing consistency and governance across API ecosystems within ServiceNow. Show full answer Show less The connector is compatible with ServiceNow releases Yokohama, Zurich, and Australia, providing a unified view of API assets and relationships for improved operational insight. ## Key Features * Automated import of organizations, managed APIs, frontends, backends, API product bundles, and consumer subscription data from Apigee Edge. * Centralized API data analysis and interaction via the API Insights workspace, allowing visibility and collaboration without needing direct Apigee Edge access. * Full lifecycle management of connector connections through the SGC Central view within the CMDB Workspace, simplifying configuration, monitoring, and troubleshooting. * Data mapping and transformation using Robust Transform Engine (RTE) and data reconciliation via Identification and Reconciliation Engine (IRE) for accurate and consistent CMDB population. * Soft deletion of CMDB Configuration Item (CI) records that are no longer discovered, marking them as Non-Operational and updating lifecycle status for managed APIs accordingly. ## Practical Use Cases for ServiceNow Customers * Maintain an end-to-end inventory of exposed and backend APIs, tracking usage and ownership. * Trace API endpoints back to underlying services to identify impact during service changes or failures, enabling incident creation. * Discover and manage Apigee Edge organizations as API gateways within the CMDB. * Track API product bundles and their relationships to managed APIs for better governance. * Monitor API consumer subscriptions and access for compliance and usage analysis. ## Configuration and Data Management Customers configure the connector through the SGC Central interface, which supports discovery, installation, and management of API connectors. Data is periodically pulled from Apigee Edge applications and mapped into specific CMDB CI classes and non-CMDB tables. The integration supports detailed staging and target tables for different API components, ensuring structured and actionable API data within the ServiceNow platform. Soft deletion ensures that outdated CMDB records are not permanently removed but marked appropriately to maintain historical context and data integrity. Use the ServiceNow® API Service Graph Connector for Apigee Edge to import API details from an Apigee Edge application into the Configuration Management Database (CMDB). ## Request apps on the Store {#api-sgc-apigee-edge__section_parent_store} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#api-sgc-apigee-edge__inline-send-to-store} ## Key features {#api-sgc-apigee-edge__section_key_features} Import organizations, managed APIs, frontends and backends, product bundles, and consumer subscription data from an Apigee Edge application into a normalized data model for consistency across other technologies. The API Insights workspace provides a centralized interface where you can analyze and interact with API data, without needing direct access to Apigee Edge, enhancing visibility, governance, and collaboration across the API estate. To learn more, see [API Insights](https://www.servicenow.com/docs/0FA9VzZDEW5Pz1URWud4zw "The ServiceNow API Insights workspace is an all-in-one application that enables you to track all your APIs. You can also use it to start workflows related to different stages in the application programming interface (API) life cycle."). ## Supported ServiceNow versions {#api-sgc-apigee-edge__section_supported_versions} * Yokohama * Zurich * Australia {#api-sgc-apigee-edge__ul_supported_versions} ## Use cases {#api-sgc-apigee-edge__section_use_cases} You can use the API Service Graph Connector for Apigee Edge to: * Maintain an end-to-end inventory of exposed and backend APIs, identifying what APIs are published, used, and by whom. * Track APIs from customer-facing endpoints to the underlying services, identifying impacted endpoints when services change or fail and creating incidents for reported issues. * Discover and inventory Apigee Edge organizations as API gateways within the CMDB. * Track API product bundles and their relationships to managed APIs. * Monitor API consumer subscriptions and consumer access details for governance and analysis. {#api-sgc-apigee-edge__ul_use_cases} ## Configuring a connection for the connector {#api-sgc-apigee-edge__section_configure_connection} You can configure a connection for the connector by using the SGC Central view in the CMDB Workspace. The SGC Central view enables you to discover and install connectors, and then effectively manage the full life cycle of creating, editing, monitoring, and debugging connections. To configure the connector using SGC Central, see [Configure API Service Graph Connector for Apigee Edge using SGC Central](https://www.servicenow.com/docs/u9Eh~Z9th7IQPYleR7KqHQ "Set up scheduled import jobs to pull in Apigee Edge data into your CMDB."). ## Data mapping {#api-sgc-apigee-edge__section_data_mapping} Data from the Apigee Edge data sources is mapped and transformed into the CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the CMDB using the Identification and Reconciliation Engine (IRE). When you complete setting up the connection, you can configure the integration to periodically pull data from an Apigee Edge application. The following table lists the data sources in the order they run, the staging tables, and the target tables as CMDB CI and non-CMDB classes for an Apigee Edge application.{#api-sgc-apigee-edge__table_data_mapping__entry__3} | Data source | Staging table | Target tables | |-|-|-| | Organization | Organization \[sn_apigee_edge_organization\] | [Apigee API Gateway](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_apigee_api_gateway) | | Managed API | Managed API \[sn_apigee_edge_managed_api\] | [Managed API](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_managed_api) [API Deployment](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_api_deployment) [DNS Alias](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_dns_alias) | | Frontend Backends | Frontend Backends \[sn_apigee_edge_frontend_backends\] | [API Backend](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_api_backend) [API Frontend](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_api_frontend) | | Consumer | Consumer \[sn_apigee_edge_consumer\] | [API Consumer](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_api_consumer) | | API Product | API Product \[sn_apigee_edge_api_product\] | [API Product Bundle](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_api_product_bundle) [Key Value](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_key_value) | | API Consumer Subscription | API Consumer Subscription \[sn_apigee_edge_api_consumer_subscription\] | [API Consumer Subscription](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_api_consumer_subscription) [Key Value](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_key_value) | | API Consumer Access | API Consumer Access \[sn_apigee_edge_api_consumer_access\] | [API](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_api) [API Consumer Access](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA#api-sgc-apigee-edge-tables__section_api_consumer_access) | [Table 1. Data mapping for Apigee Edge] {#api-sgc-apigee-edge__table_data_mapping} For more information on where data is saved when pulling data from an Apigee Edge application, see [Target tables for storing API Service Graph Connector for Apigee Edge data](https://www.servicenow.com/docs/VM53~uEgOpgGyTG2byJoVA "When you complete setting up the connection, you can configure the integration to periodically pull data from an Apigee Edge application. The data is saved in tables that extend from the Configuration item [cmdb_ci] classes and other non-CMDB tables."). You can use the IntegrationHub ETL app to view the data maps. See [IntegrationHub ETL](https://www.servicenow.com/docs/MvUnD_GHFcty25xoT_q32Q "Use the IntegrationHub ETL store app to create and manage ETL transform maps, which integrate third-party data into the CMDB or into non-CMDB tables without compromising the integrity of data. IntegrationHub ETL provides a simplified user interface that guides you through the integration process end-to-end, including a test integration run of sample data.") for more information. ## Record removal process {#api-sgc-apigee-edge__section_record_removal} The connector supports soft deletion for CMDB CI classes only, meaning records aren't permanently removed from the system. Instead, any CMDB CI records not discovered during the last scheduled job run are marked as Non-Operational. For Managed API \[cmdb_ci_managed_api\] records, the connector also sets the Life cycle stage field to End of Life and the Life cycle stage status field to Retired.