---
schema_version: "1"
id: d608f8179575ed323d92b462134a98685a577ae251d7cc5963c10b32ad74c918
title: "Use Case 2: Organization-Owned API Exposed to a Non-Organization-Owned API Consumer"
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.9/flex-architecture-uc2.md
canonical_url: https://docs.mulesoft.com/gateway/1.9/flex-architecture-uc2
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 9364cc57e30731d00cb9a6cb262a54feb7dfac50ea187de20e1c86c01fc32765
description: MuleSoft Documentation Site
release: "1.9"
latest: false
---
---
product: Omni Gateway
version: 1.9
---

# Use Case 2: Organization-Owned API Exposed to a Non-Organization-Owned API Consumer

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Use case two covers all patterns of a scenario in which an organization-owned API is exposed to a
non-organization-owned API consumer; for example, when a user makes a request to your public-facing
API.

## Pattern 5: Organization Internal API exposed to a Non-Organization External Consumer

In pattern five, the infrastructure of the organization-owned API is isolated from the API consumer.
The consumer can access the exposed API only via the internet. In this use case, you deploy Flex
Gateway as an ingress.

![Consumer application requests pass through the internet and a firewall before reaching Flex Gateway.](/mulesoft/current/en-us/gateway/1.9/_images/ad-uc-1-p-2.png)

The following diagram shows the physical implementation of a scenario in which an organization-owned
internal API is exposed to a non-organization-owned external consumer on Kubernetes. The diagram
assumes that the firewall terminates the incoming external mTLS connection.

![A detailed view of pattern five, which contains the necessary services to support Flex Gateway](/mulesoft/current/en-us/gateway/1.9/_images/ad-uc-2-p-5-physical.png)

## Pattern 6: Organization External API exposed to a Non-Organization External Consumer

In pattern six, Flex Gateway acts as an intermediary between two external network entities. Flex
Gateway runs as an ingress and egress that applies secure communication and policy enforcement.

![Flex Gateway acts as an intermediary between an external application and external API.](/mulesoft/current/en-us/gateway/1.9/_images/ad-uc-1-p-4.png)

The following diagram shows the physical implementation of a scenario in which an organization
external API is exposed to an non-organization external consumer on Kubernetes. The diagram assumes
that the firewall terminates the external mTLS connections.

![A detailed view of pattern six, which contains the necessary services to support Flex Gateway](/mulesoft/current/en-us/gateway/1.9/_images/ad-uc-2-p-6-physical.png)

## See Also

- [Use Case 1: Organization-Owned API Exposed to an Organization-Owned API Consumer](https://docs.mulesoft.com/gateway/1.9/flex-architecture-uc1)

- [Use Case 3: Non-Organization-Owned API Exposed to an Organization-Owned API Consumer](https://docs.mulesoft.com/gateway/1.9/flex-architecture-uc3)

- [Use Case 4: Non-Organization-Owned API Exposed to a Non-Organization-Owned API Consumer](https://docs.mulesoft.com/gateway/1.9/flex-architecture-uc4)