"},{"ID":10222,"user_firstname":"Jill","user_lastname":"Edstrom-Shoemaker","nickname":"Jill Edstrom-Shoemaker","user_nicename":"jedstrom","display_name":"Jill Edstrom-Shoemaker","user_email":"JEdstrom@esri.com","user_url":"","user_registered":"2019-11-22 17:01:50","user_description":"Jill leads the ArcGIS Enterprise and data management product management teams. She focuses her time on enabling customers to get the most they can out of their ArcGIS software by aligning product strategy with real world implementation needs. Outside of work, Jill is working her way through visiting all the U.S. national parks, though she is more often found reading a good book with her dog by her side.","user_avatar":"
"}],"short_description":"ArcGIS Enterprise delivers enterprise\u2011ready GIS that integrates, extends, and adapts. Discover how to extend your existing systems.","flexible_content":[{"acf_fc_layout":"content","content":"Enterprise environments are complex, made up of business systems, security frameworks, data platforms, compliance requirements, and custom applications. Modern enterprises don\u2019t operate in silos, and neither should their GIS.<\/span>\u00a0<\/span><\/p>\n From the beginning, ArcGIS Enterprise has been built to be flexible, adaptable, and deeply integrated into the systems organizations already rely on. It ensures organizations can bring meaningful GIS capabilities directly into their existing workflows, without rearchitecting their systems or abandoning their current investments.<\/span>\u00a0<\/span><\/p>\n At\u00a0a high level, extensibility in ArcGIS Enterprise\u00a0follows\u00a0three\u00a0<\/span>patterns<\/span>: Integrate. Extend. Intercept. These three patterns are enabled through APIs, webhooks, custom web tools, and the ArcGIS Enterprise SDK\u2014which is included with an ArcGIS Enterprise license. These extensibility patterns equip developers, system integrators, and business partners to extend ArcGIS Enterprise with new logic, capabilities, and data connections.<\/span>\u00a0<\/span><\/p>\n"},{"acf_fc_layout":"sidebar","content":" Skip to a specific ArcGIS Enterprise extensibility pattern:<\/p>\n Integrate<\/a> | Extend<\/a> | Intercept<\/a><\/p>\n","image_reference":false,"layout":"standard","image_reference_figure":"","snippet":"","spotlight_name":"","section_title":"","position":"Center","spotlight_image":false},{"acf_fc_layout":"content","content":" <\/p>\n Integration\u00a0<\/span>is about making GIS part of enterprise-wide processes. Organizations today depend on event-driven systems, automation pipelines, and interconnected applications. One of the primary ways this can be done in ArcGIS Enterprise is with <\/span>webhooks. With webhooks,\u00a0ArcGIS Enterprise can connect with\u00a0<\/span>external business systems\u00a0<\/span>in real time\u2014triggering workflows, notifying downstream systems, and responding to change as it happens.<\/span>\u00a0<\/span><\/p>\n In ArcGIS Enterprise, there are two types of webhooks: organization webhooks and service webhooks.<\/span>\u00a0<\/span><\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2959168,"id":2959168,"title":"extensibility blog images-1-web hooks","filename":"extensibility-blog-images-1-web-hooks.png","filesize":221735,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-enterprise\/announcements\/extending-whats-possible-with-arcgis-enterprise\/extensibility-blog-images-1-web-hooks","alt":"","author":"370372","description":"","caption":"","name":"extensibility-blog-images-1-web-hooks","status":"inherit","uploaded_to":2959167,"date":"2026-03-04 16:41:45","modified":"2026-03-04 16:41:45","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":1920,"height":1080,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks.png","medium-width":464,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks.png","medium_large-width":768,"medium_large-height":432,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks.png","large-width":1920,"large-height":1080,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks-1536x864.png","1536x1536-width":1536,"1536x1536-height":864,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks.png","2048x2048-width":1920,"2048x2048-height":1080,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks-826x465.png","card_image-width":826,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-1-web-hooks.png","wide_image-width":1920,"wide_image-height":1080}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":" Organization webhooks <\/strong>can be configured\u00a0to\u00a0listen for events on items, users, groups, and roles.\u00a0An example of this is\u00a0a webhook\u00a0being\u00a0configured to trigger when a specific user signs in to the Enterprise\u00a0portal\u00a0or any content has been shared to a group.\u00a0\u00a0<\/span><\/p>\n Service webhooks<\/strong> can be configured to listen to specific interactions associated with feature services and geoprocessing services.\u00a0\u00a0Feature service webhooks can be created for both hosted and by-reference feature services. The webhook can be configured to send a message when edit operations, such as create, update and delete events occur. Geoprocessing service webhooks can be triggered whenever a job ends \u2013 whether that job is successful, it was stopped, or it failed.\u00a0<\/span><\/p>\n These webhooks can help bridge the gap between GIS and other enterprise platforms. A change in a layer, the completion of a geoprocessing task, or an update to a service can automatically initiate actions in external systems.<\/span>\u00a0<\/span><\/p>\n Read more about webhooks in\u00a0our\u00a0<\/span>Introduction to ArcGIS Enterprise webhooks blog<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n This\u00a0integration\u00a0pattern\u00a0ensures that\u00a0GIS\u00a0doesn\u2019t\u00a0operate\u00a0in isolation. Instead, it becomes part of the\u00a0organization\u2019s\u00a0<\/span>enterprise architecture,\u00a0<\/span>supporting automation, orchestration, and enterprise-scale coordination.<\/span>\u00a0<\/span><\/p>\n"},{"acf_fc_layout":"content","content":" <\/p>\n While integration connects ArcGIS Enterprise outward, extension expands what it can do inward\u00a0so\u00a0organization\u00a0can support\u00a0unique workflows, proprietary processes, and specialized data sources.\u00a0<\/span>ArcGIS Enterprise\u2019s out-of-the-box capabilities are powerful, but when organizations need to go further, this extension pattern is powered by two key mechanisms: server object extensions (SOEs) and custom data feeds. <\/span>\u00a0<\/span><\/p>\n <\/p>\n Server Object Extensions (SOEs)\u00a0<\/strong> For example, an SOE can support on-the-fly calculations, enforce specialized transformations, or embed proprietary business logic directly into a service. Once deployed, that logic is exposed through the ArcGIS Server REST API for use by custom applications. These are nonstandard APIs designed for custom applications, so will not work with out of the box apps like ArcGIS Pro or Map Viewer but can be configured to work with custom applications, such as those built with the ArcGIS Maps SDK for JavaScript<\/a>. They allow organizations to build highly tailored solutions that reflect their unique business needs and help services do more than they were originally designed to do.<\/p>\n Read more about SOEs in the\u00a0Overview of developing SOEs product documentation<\/a>.<\/p>\n <\/p>\n Custom Data Feeds\u00a0<\/strong><\/p>\n Extending ArcGIS Enterprise isn\u2019t only about adding new operations; it\u2019s also about expanding access to data. With custom data feeds, ArcGIS Enterprise can connect directly to data sources that aren\u2019t natively supported, without migration or duplication.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2959204,"id":2959204,"title":"extensibility blog images-2-custom data feeds","filename":"extensibility-blog-images-2-custom-data-feeds.png","filesize":188805,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-enterprise\/announcements\/extending-whats-possible-with-arcgis-enterprise\/extensibility-blog-images-2-custom-data-feeds","alt":"","author":"370372","description":"","caption":"Custom data feeds are now available in ArcGIS Enterprise on Windows, Linux, and Kubernetes","name":"extensibility-blog-images-2-custom-data-feeds","status":"inherit","uploaded_to":2959167,"date":"2026-03-04 17:40:48","modified":"2026-03-04 17:41:10","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":1920,"height":1080,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds.png","medium-width":464,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds.png","medium_large-width":768,"medium_large-height":432,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds.png","large-width":1920,"large-height":1080,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds-1536x864.png","1536x1536-width":1536,"1536x1536-height":864,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds.png","2048x2048-width":1920,"2048x2048-height":1080,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds-826x465.png","card_image-width":826,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-2-custom-data-feeds.png","wide_image-width":1920,"wide_image-height":1080}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":" With a custom data provider created specifically to the data source, ArcGIS Enterprise can fetch and read data from an external source while the data remains in its original location. A feature service is created in ArcGIS Enterprise that reflects the source data, and updates in the source can be surfaced in the service, depending on how the feed is configured. This approach unlocks data that would otherwise be inaccessible within ArcGIS workflows.<\/span>\u00a0<\/span><\/p>\n And with recent updates from 11.5 bringing custom data feeds to ArcGIS Enterprise on Kubernetes, extensibility capabilities continue to evolve across deployment models, ensuring parity and flexibility regardless of how your ArcGIS Enterprise is deployed.<\/span>\u00a0<\/span><\/p>\n Read more about custom data feeds in\u00a0our\u00a0<\/span>New in ArcGIS Enterprise 11.1: custom data feeds blog<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n"},{"acf_fc_layout":"content","content":" <\/p>\n Sometimes organizations don\u2019t just need to connect or extend; they need to intervene. They need to enforce compliance, audit activity, validate data, inject security controls, or apply business rules to every request flowing through the system.<\/span>\u00a0<\/span><\/p>\n This is where interception, the third and final extensibility pattern, comes into play. ArcGIS Enterprise provides two primary interception mechanisms: service interceptors and server object interceptors (SOIs):<\/span>\u00a0<\/span><\/p>\n <\/p>\n Service Interceptors<\/b><\/p>\n Released in ArcGIS Enterprise 12.0 on Windows and Linux, service interceptors operate at the web services tier and expand standard REST requests and responses through pre- and post-processing.\u00a0<\/span><\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2959169,"id":2959169,"title":"extensibility blog images-3-service interceptors","filename":"extensibility-blog-images-3-service-interceptors-e1772645752397.png","filesize":65039,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-e1772645752397.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-enterprise\/announcements\/extending-whats-possible-with-arcgis-enterprise\/extensibility-blog-images-3-service-interceptors","alt":"","author":"370372","description":"","caption":"","name":"extensibility-blog-images-3-service-interceptors","status":"inherit","uploaded_to":2959167,"date":"2026-03-04 16:42:24","modified":"2026-03-04 16:42:24","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":920,"height":518,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-e1772645752397.png","medium-width":464,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-e1772645752397.png","medium_large-width":768,"medium_large-height":432,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-e1772645752397.png","large-width":920,"large-height":518,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-1536x864.png","1536x1536-width":1536,"1536x1536-height":864,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-e1772645752397.png","2048x2048-width":920,"2048x2048-height":518,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-826x465.png","card_image-width":826,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-3-service-interceptors-e1772645752397.png","wide_image-width":920,"wide_image-height":518}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":" Written in Java, they allow organizations to use high-level APIs to intercept web service traffic without necessarily requiring knowledge of the underlying service runtime. They are not tied to individual services and are not limited to map or image services; they can be configured to be applied to all web services published to ArcGIS Enterprise. Common use cases include auditing and logging, enforcing security compliance, access control, and applying customer-specific business logic.\u00a0<\/span><\/p>\n One of the most powerful aspects of service interceptors is their ability to enable custom workflows at the request and response level without changing client applications or <\/span>fortifying\u00a0<\/span>backend services.\u00a0This allows\u00a0organizations\u00a0to\u00a0implement enterprise-wide logic in a centralized, scalable way.<\/span>\u00a0<\/span><\/p>\nIntegrate: Connecting GIS to the Broader Business<\/strong><\/h1>\n
<\/h2>\n
Extend: Expanding What ArcGIS Enterprise Can Do\u00a0<\/strong><\/h1>\n
\nSOEs allow organizations to add new business logic to referenced map and image services. Built using Java or .NET, SOEs introduce new REST operations, enabling services to perform tasks they otherwise would not be able to do. <\/span><\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2959252,"id":2959252,"title":"extensibility blog images-6","filename":"extensibility-blog-images-6.png","filesize":312268,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-enterprise\/announcements\/extending-whats-possible-with-arcgis-enterprise\/extensibility-blog-images-6","alt":"","author":"370372","description":"","caption":"","name":"extensibility-blog-images-6","status":"inherit","uploaded_to":2959167,"date":"2026-03-04 19:33:03","modified":"2026-03-04 19:33:03","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":1920,"height":1080,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6.png","medium-width":464,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6.png","medium_large-width":768,"medium_large-height":432,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6.png","large-width":1920,"large-height":1080,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6-1536x864.png","1536x1536-width":1536,"1536x1536-height":864,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6.png","2048x2048-width":1920,"2048x2048-height":1080,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6-826x465.png","card_image-width":826,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/03\/extensibility-blog-images-6.png","wide_image-width":1920,"wide_image-height":1080}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"<\/h2>\n
Intercept: Injecting Logic into Requests and Responses<\/strong><\/h1>\n