# Interlink Service Communication

**URL:** <https://forums.broadleafcommerce.com/t/interlink-service-communication/103>\
**Category:** Shared Concepts\
**Tags:** shared-concepts\
**Created:** [March 25, 2026, 2:01am UTC](https://forums.broadleafcommerce.com/t/interlink-service-communication/103 "2026-03-25T02:01:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![broadleaf-moderator](https://yyz1.discourse-cdn.com/flex011/user_avatar/forums.broadleafcommerce.com/broadleaf-moderator/32/7_2.png) [@broadleaf-moderator](https://forums.broadleafcommerce.com/u/broadleaf-moderator)\
**Post date:** [March 25, 2026, 2:01am UTC](https://forums.broadleafcommerce.com/t/interlink-service-communication/103/1 "2026-03-25T02:01:09Z")

</div>

We received a support ticket asking about the best way to handle service-to-service communication when upgrading from Broadleaf 2.0.2 to 2.2.1. Specifically, the team wanted a way to call other services that works seamlessly whether the target API is co-located in the same flex package or running as a separate remote microservice.

To address this situation, we’ve introduced (and further enhanced) the **Interlink** provider approach. Interlink provides a single, unified structure for calling other services, abstracting away the underlying transport mechanism.

Details on interlink can be found at the official documentation here: [Interlink Requests - Broadleaf Dev Central](https://developer.broadleafcommerce.com/shared-concepts/interlink)