--- sourceDocument: Australia ServiceNow AI Platform Capabilities sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform Release : - australia ft:locale : - de-DE ft:publication_title : - Australia ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Kong Konnect # API Service Graph Connector for Kong Konnect {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer Use the ServiceNow® API Service Graph Connector for Kong Konnect to import API details from a Kong Konnect service into the Configuration Management Database (CMDB). ## Request apps on the Store {#api-sgc-kong-konnect__section_wmp_t4l_pgc} 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://docs.servicenow.com/bundle/store-release-notes/page/release-notes/store/sn-store-release-notes.html).{#api-sgc-kong-konnect__inline-send-to-store} ## Key features {#api-sgc-kong-konnect__section_j1v_t4l_pgc} Import data 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 Kong Konnect, enhancing visibility, governance, and collaboration across the API estate. To learn more, see [API Insights](https://servicenow-prod.fluidtopics.net/T5UKVAkX3KxuwptynWVOzQ "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-kong-konnect__section_yj1_54l_pgc} * Xanadu * Yokohama * Zurich {#api-sgc-kong-konnect__ul_txy_fhs_2bc} ## Use cases {#api-sgc-kong-konnect__section_fqf_54l_pgc} You can use the API Service Graph Connector for Kong Konnect to: * Maintain an end-to-end inventory of defined 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. * Address vulnerabilities and security incidents related to API endpoints and create compliance requirements to measure against. {#api-sgc-kong-konnect__ul_abl_qgj_4bc} ## Configuring a connection for the connector {#api-sgc-kong-konnect__section_hsl_54l_pgc} You can configure a connection for the connector by using the SGC Central view in the CMDB Workspace. The 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 Kong Konnect using SGC Central](https://servicenow-prod.fluidtopics.net/_GOOSuf_hdEOhYzQI5rhGQ "Set up scheduled import jobs to pull in Kong Konnect data into your CMDB."). ## Data mapping {#api-sgc-kong-konnect__section_d5q_54l_pgc} Data from the Kong Konnect 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 a Kong Konnect service. The following table lists the data sources in the order they run, the staging tables, and the target tables as CMDB CI classes and non-CMDB tables for a Kong Konnect service.{#api-sgc-kong-konnect__table_wfw_1pl_pgc__entry__3} | Data source | Staging table | Target tables | |-|-|-| | Gateway | Gateway \[sn_kong_konnect_gateway\] | [Kong Gateway](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_hzj_zcb_vgc) [DNS Alias](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_rhc_rbt_wgc) [Logical Datacenter](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_ohc_rbt_wgc) [Cloud Service Account](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_thc_rbt_wgc) [Key Value](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_bfs_fdb_vgc) | | Data Plane Node | Data Plane Node \[sn_kong_konnect_data_plane_node\] | [Kong Data Plane Node](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_kmr_wjb_c3c) | | Load Balancer | Load Balancer \[sn_kong_konnect_load_balancer\] | [Kong Load Balancer](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_jy2_1db_vgc) | | Target | Target \[sn_kong_konnect_target\] | [Kong Target](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_nry_1db_vgc) | | Services | Services \[sn_kong_konnect_services\] | [Managed API](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_plj_bdb_vgc) [API Backend](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_vqb_cdb_vgc) [Key Value](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_bfs_fdb_vgc) | | Routes | Routes \[sn_kong_konnect_routes\] | [API Frontend](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_frv_cdb_vgc) | | Consumer | Consumer \[sn_kong_konnect_consumer\] | [API Consumer](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_akr_ddb_vgc) | | Policy | Policy \[sn_kong_konnect_policy\] | [API Policy](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_jj4_2db_vgc) | | Developers | Developers \[sn_kong_konnect_developers\] | [API Consumer](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_akr_ddb_vgc) | | Applications | Applications \[sn_kong_konnect_applications\] | [API Consumer Subscription](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_zfb_3j3_lhc) | | API Consumer Access | API Consumer Access \[sn_kong_konnect_api_consumer_access\] | [API Consumer Access](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g#api-sgc-kong-konnect-tables__section_occ_gk3_lhc) | [Tabelle : 1. Data mapping for Kong Konnect] {#api-sgc-kong-konnect__table_wfw_1pl_pgc} For more information on where data is saved when pulling data from a Kong Konnect service, see [Target tables for storing API Service Graph Connector for Kong Konnect data](https://servicenow-prod.fluidtopics.net/RJ4dG4nZOfOAc~w5tdpG3g "When you complete setting up the connection, you can configure the integration to periodically pull data from a Kong Konnect 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://servicenow-prod.fluidtopics.net/o3eK_l0nhtAcQ_AgXuZ95Q "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-kong-konnect__section_ctw_54l_pgc} The connector supports soft deletion for CMDB CI classes only, meaning records are not permanently removed from the system. Instead, any CMDB CI records not discovered during the last scheduled job run are marked as Non-Operational.