{"id":513697,"date":"2019-03-22T16:42:28","date_gmt":"2019-03-22T15:42:28","guid":{"rendered":"https:\/\/www.devoteam.com\/expert-view\/api-integration-patterns\/"},"modified":"2025-06-12T10:53:52","modified_gmt":"2025-06-12T08:53:52","slug":"api-integration-patterns","status":"publish","type":"expert-view","link":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/","title":{"rendered":"API Integration Patterns"},"content":{"rendered":"<h2>Experience-based APIs<\/h2>\n<p>As part of any API Management platform rollout project, a new API publication pattern targeting API consumers should be promoted: <strong>Experience based APIs<\/strong>. This approach of API integration patterns will become the driver for <em>Self-service API Management<\/em>, enabling <em>consumer specific API wrappers<\/em> that are <em>designed and implemented by the consuming teams<\/em>. In addition to that, this article provides an overview of the pattern, emphasizing the benefits and value created by its adoption.<\/p>\n<h3>1. API Proxy is a pattern where fa\u00e7ade APIs sit between consumer apps and legacy APIs<\/h3>\n<p><a href=\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/api-proxy-pattern.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-10541 size-full\" src=\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/api-proxy-pattern.png\" alt=\"\" width=\"793\" height=\"350\" \/><\/a><\/p>\n<p>Fa\u00e7ades and Proxies of API integration patterns are a well-known pattern of Integration Architects with traditional EAI and SOA knowledge. They bring multiple benefits and offer a wide set of capabilities that can enrich the functionality offered by the legacy APIs being proxied.<\/p>\n<p>Typical capabilities supported by API proxies are:<\/p>\n<ul>\n<li>Light API composition<\/li>\n<li>Routing<\/li>\n<li>Message transformation<\/li>\n<li>Protocol bridging<\/li>\n<li>API aggregation<\/li>\n<li>Policy enforcement (security, threat, quotas, etc.)<\/li>\n<li>Caching<\/li>\n<li>Mock-up creation<\/li>\n<li>Canary testing \/ AB testing<\/li>\n<li>API anonymization<\/li>\n<\/ul>\n<p>Understanding these integration patterns is the crucial first step. Once mastered, these methods provide the foundation for more advanced applications, such as creating the seamless connections that power <a href=\"https:\/\/devoteam.info\/be\/expert-view\/api-driven-ai-the-power-of-connected-intelligence\/\" target=\"_blank\" rel=\"noopener\"><strong>API-driven AI and connected intelligence<\/strong><\/a>.<\/p>\n<h3>2. Experience based APIs leverage API Proxies to enable consumer specific API publication<\/h3>\n<p>The Proxy pattern can be extended to enable the creation of multiple Proxy endpoints, each one dedicated to a specific API consumer. These new Proxy endpoints will be designed, developed and configured focusing exclusively on the business requirements of their API consumers. Proxy capabilities (transformation, protocol bridging, etc.) can be applied per endpoint, leading to the availability of tailored proxy endpoints which can expose functionality somewhat disparate than the original legacy API.<\/p>\n<p><a href=\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/proxy-endpoints.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-10551 size-full\" src=\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/proxy-endpoints.png\" alt=\"\" width=\"631\" height=\"416\" \/><\/a><\/p>\n<p>It is also a good practice to make available a generic \u201cone size fits all\u201d Proxy endpoint to support consumers that need no tailoring of the legacy API business function. Organizations have been successfully exposing and consuming these generic endpoints for a long time, and their immediate decommissioning would not make sense.<\/p>\n<p>There are three key principles that must not be disregarded when implementing the Experience based APIs pattern. Their aim is to ensure maximum value can be derived from the pattern adoption.<\/p>\n<ul>\n<li>It is important to understand the consumers of an API. Only then a decision can be made if Experience and\/or a General-Purpose endpoints are required<span lang=\"EN-GB\">\u00a0<\/span><\/li>\n<li><span lang=\"EN-GB\">Most APIs are designed by providers and focus on data model purity. Experience based APIs target optimizations and\/or performance and not the data model<\/span><\/li>\n<li>Many APIs are designed by API teams having in mind facilitated support. The exposure of Experience based APIs can bring extra complexity to the support processes<\/li>\n<\/ul>\n<h3>3. API Management platforms will promote a shift to an Experience based APIs architecture<\/h3>\n<ol style=\"list-style-type: upper-roman;\">\n<li><strong>The change drivers<\/strong><br \/>\nGeneral-Purpose APIs are currently exposed, providing reusable functionality to multiple user-facing applications. However, Desktop, Mobile, Wearables and other devices\u2019 experiences differ drastically \u2013 the functionality exposed is also different. Additionally, existing legacy SOAP services are verbose and provide less suitable payload formats<\/li>\n<li><strong>Suited solution<br \/>\n<\/strong>Promote consumer grade <b>Experience based APIs<\/b> as a core integration pattern, enabling <i>Self-Service API Management<\/i>, for efficient publication of consumer specific APIs:<br \/>\n&#8211; App specific APIs<br \/>\n&#8211; Device specific APIs<br \/>\nSelf-Service is crucial to the pattern since it empowers API consumers to design, implement and configure their own API <i>Proxy endpoints<\/i> \u2013 API consumers will have full control and ownership of the <i>Proxy endpoints<\/i> they consume.<\/li>\n<li><strong>Predicted benefits<br \/>\n<\/strong>Contribute to a smoother customer journey and exceptional customer engagement.<br \/>\nSupport &#8220;Mobile First&#8221; strategy, delivering APIs that:<br \/>\n&#8211; Require fewer calls \u2013 for increased battery life and limited data plans<br \/>\n&#8211; Expose less data \u2013 for superior app performance<\/li>\n<\/ol>\n<h3>4. Experience based APIs and Self-Service API Management should be encouraged for 3 use cases<\/h3>\n<p><a href=\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/self-service-api-management.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-10561 size-full\" src=\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/self-service-api-management.png\" alt=\"\" width=\"808\" height=\"311\" \/><\/a><br \/>\nWould you like to know more about Experience based APIs, or API integration patterns?\u00a0We can assist your organization with workshops on the topic. Our consultants have led API Management platform rollout processes in multiple domains and will guide you in the creation of an API center of expertise delivering consumer grade APIs.<\/p>\n<div class=\"block-fullwidth-dark\">\n<div class=\"row-more clearfix\"><a class=\"bt-more\" href=\"https:\/\/nl.devoteam.com\/offer\/agile-it\/api-management-consultancy-implementation\/\">Our API Management offer<\/a><\/div>\n<\/div>\n<h2>API Management blogs, news &amp; cases<\/h2>\n<ul>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/offer\/agile-it\/api-management-consultancy-implementation\/\">Offer: API Management<\/a><\/strong><\/li>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/en\/integration\/services-for-eai-api-management\/\">Offer:\u00a0EAI and API Management<\/a><\/strong><\/li>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/the-future-of-api-management\/\">Whitepaper: The Future of API Management<\/a><\/strong><\/li>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/en\/case-study\/api-management-liberty-global-inc\/\">Case Study: API Management at Liberty Global Inc.<\/a><\/strong><\/li>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/en\/case-study\/eneco-using-api-management-platform-right-way\/\">Case Study:\u00a0Eneco: using their API Management Platform the right way<\/a><\/strong><\/li>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/en\/blog-post\/self-service-api-management-part-1\/\">Blog series: Self-service API Management<\/a><\/strong><\/li>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/en\/blog-post\/axway-api-management-an-introduction\/\">Blog series: Axway API Management<\/a><\/strong><\/li>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/blog-post\/api-management-architecture-introduction\/\">Blog: API Management Architecture &#8211; an introduction<\/a><\/strong><\/li>\n<li><strong><a href=\"https:\/\/nl.devoteam.com\/en\/blog-post\/best-breed-api-management-platforms\/\">Blog: Best breed of API Management Platforms<\/a><\/strong><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Experience-based APIs As part of any API Management platform rollout project, a new API publication pattern targeting API consumers should be promoted: Experience based APIs. This approach of API integration patterns will become the driver for Self-service API Management, enabling consumer specific API wrappers that are designed and implemented by the consuming teams. In addition [&hellip;]<\/p>\n","protected":false},"featured_media":0,"template":"","categories":[1058],"tags":[1724],"industry":[],"class_list":["post-513697","expert-view","type-expert-view","status-publish","hentry","category-business-platforms","tag-uk-import-be"],"acf":[],"cards":"\n\t<div class=\"single-post-card\">\n\n\t\t\n\n\t\t\n\t\t<div class=\"wp-block-group is-vertical is-layout-flex wp-container-core-group-is-layout-43282307 wp-block-group-is-layout-flex\">\n\t<p style=\"font-style:normal;font-weight:700\" class=\"has-link-color wp-elements-1 wp-block-lp-post-type has-text-color has-primary-color has-small-font-size\">Expert View<\/p>\n\n\t\t\n\t\t<h3 style=\"font-style:normal;font-weight:400\" class=\"wp-block-post-title has-base-font-size\"><a href=\"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/\" target=\"_self\" >API Integration Patterns<\/a><\/h3><\/div>\n\t\t\n\t<\/div>\n\n","yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>API Integration Patterns | Devoteam<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"API Integration Patterns\" \/>\n<meta property=\"og:description\" content=\"Experience-based APIs As part of any API Management platform rollout project, a new API publication pattern targeting API consumers should be promoted: Experience based APIs. This approach of API integration patterns will become the driver for Self-service API Management, enabling consumer specific API wrappers that are designed and implemented by the consuming teams. In addition [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"Devoteam\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-12T08:53:52+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/axway-api-management.jpeg\" \/>\n\t<meta property=\"og:image:width\" content=\"1280\" \/>\n\t<meta property=\"og:image:height\" content=\"853\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/api-integration-patterns\\\/\",\"url\":\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/api-integration-patterns\\\/\",\"name\":\"API Integration Patterns | Devoteam\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/devoteam.info\\\/be\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/api-integration-patterns\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/api-integration-patterns\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/devoteam.info\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/api-proxy-pattern.png\",\"datePublished\":\"2019-03-22T15:42:28+00:00\",\"dateModified\":\"2025-06-12T08:53:52+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/api-integration-patterns\\\/#breadcrumb\"},\"inLanguage\":\"en-BE\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/api-integration-patterns\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-BE\",\"@id\":\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/api-integration-patterns\\\/#primaryimage\",\"url\":\"https:\\\/\\\/devoteam.info\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/api-proxy-pattern.png\",\"contentUrl\":\"https:\\\/\\\/devoteam.info\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/api-proxy-pattern.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/api-integration-patterns\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/devoteam.info\\\/be\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Expert View\",\"item\":\"https:\\\/\\\/devoteam.info\\\/be\\\/expert-view\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"API Integration Patterns\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/devoteam.info\\\/be\\\/#website\",\"url\":\"https:\\\/\\\/devoteam.info\\\/be\\\/\",\"name\":\"Devoteam\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/devoteam.info\\\/be\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-BE\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"API Integration Patterns | Devoteam","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/","og_locale":"en_US","og_type":"article","og_title":"API Integration Patterns","og_description":"Experience-based APIs As part of any API Management platform rollout project, a new API publication pattern targeting API consumers should be promoted: Experience based APIs. This approach of API integration patterns will become the driver for Self-service API Management, enabling consumer specific API wrappers that are designed and implemented by the consuming teams. In addition [&hellip;]","og_url":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/","og_site_name":"Devoteam","article_modified_time":"2025-06-12T08:53:52+00:00","og_image":[{"width":1280,"height":853,"url":"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/axway-api-management.jpeg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/","url":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/","name":"API Integration Patterns | Devoteam","isPartOf":{"@id":"https:\/\/devoteam.info\/be\/#website"},"primaryImageOfPage":{"@id":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/#primaryimage"},"image":{"@id":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/#primaryimage"},"thumbnailUrl":"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/api-proxy-pattern.png","datePublished":"2019-03-22T15:42:28+00:00","dateModified":"2025-06-12T08:53:52+00:00","breadcrumb":{"@id":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/#breadcrumb"},"inLanguage":"en-BE","potentialAction":[{"@type":"ReadAction","target":["https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/"]}]},{"@type":"ImageObject","inLanguage":"en-BE","@id":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/#primaryimage","url":"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/api-proxy-pattern.png","contentUrl":"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/11\/api-proxy-pattern.png"},{"@type":"BreadcrumbList","@id":"https:\/\/devoteam.info\/be\/expert-view\/api-integration-patterns\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/devoteam.info\/be\/"},{"@type":"ListItem","position":2,"name":"Expert View","item":"https:\/\/devoteam.info\/be\/expert-view\/"},{"@type":"ListItem","position":3,"name":"API Integration Patterns"}]},{"@type":"WebSite","@id":"https:\/\/devoteam.info\/be\/#website","url":"https:\/\/devoteam.info\/be\/","name":"Devoteam","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/devoteam.info\/be\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-BE"}]}},"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false},"uagb_author_info":{"display_name":"julien.lemarchal","author_link":"https:\/\/devoteam.info\/be\/author\/"},"uagb_comment_info":0,"uagb_excerpt":"Experience-based APIs As part of any API Management platform rollout project, a new API publication pattern targeting API consumers should be promoted: Experience based APIs. This approach of API integration patterns will become the driver for Self-service API Management, enabling consumer specific API wrappers that are designed and implemented by the consuming teams. In addition&hellip;","_links":{"self":[{"href":"https:\/\/devoteam.info\/be\/wp-json\/wp\/v2\/expert-view\/513697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devoteam.info\/be\/wp-json\/wp\/v2\/expert-view"}],"about":[{"href":"https:\/\/devoteam.info\/be\/wp-json\/wp\/v2\/types\/expert-view"}],"version-history":[{"count":0,"href":"https:\/\/devoteam.info\/be\/wp-json\/wp\/v2\/expert-view\/513697\/revisions"}],"wp:attachment":[{"href":"https:\/\/devoteam.info\/be\/wp-json\/wp\/v2\/media?parent=513697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devoteam.info\/be\/wp-json\/wp\/v2\/categories?post=513697"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devoteam.info\/be\/wp-json\/wp\/v2\/tags?post=513697"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/devoteam.info\/be\/wp-json\/wp\/v2\/industry?post=513697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}