---
schema_version: "1"
id: f8adefd145f6401f48f0a9a481c7535418946763c7140e378b5eee67bae2d511
title: "Use Case 3: Non-Organization-Owned API Exposed to an Organization-Owned API Consumer"
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.13/gateway-architecture-uc3.md
canonical_url: https://docs.mulesoft.com/gateway/1.13/gateway-architecture-uc3
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 1a9fb5da980ac3bbc3246153ffd69141aa190fae3b57b70ef603e2137dbad7aa
description: MuleSoft Documentation Site
release: "1.13"
latest: false
---
---
product: Omni Gateway
version: 1.13
---

# Use Case 3: Non-Organization-Owned API Exposed to an Organization-Owned API Consumer

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

Use case three covers all patterns of a scenario in which a non-organization-owned API is exposed to
an organization-owned API consumer.

Use case examples:

- A payments service must obtain exchange rates from an external service provider.

- An internal API Consumer accesses the organization’s external ServiceNow instance (SaaS service).

## Pattern 7: Non-Organization External API exposed to an Organization Internal Consumer

In pattern seven, you deploy Omni Gateway as an egress. You can use Omni Gateway to monitor,
control, and enrich the flows to external services. Additionally, you can rate limit external access
and track metrics and analytics.

![Omni Gateway acts as an egress to monitor incoming traffic from the external API.](/mulesoft/current/en-us/gateway/1.13/_images/ad-uc-1-p-3.png)

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

![A detailed view of pattern](/mulesoft/current/en-us/gateway/1.13/_images/ad-uc-3-p-7-physical.png)

## Pattern 8: Non-Organization External API exposed to an Organization External Consumer

In pattern eight, Omni Gateway acts as an intermediary between two organization external entities.
Omni Gateway runs as an ingress and egress that applies secure communication and policy enforcement.

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

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

![A detailed view of pattern eight, which contains the necessary services to support Omni Gateway](/mulesoft/current/en-us/gateway/1.13/_images/ad-uc-3-p-8-physical.png)

## See Also

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

- [Use Case 2: Organization-Owned API Exposed to a Non-Organization-Owned API Consumer](https://docs.mulesoft.com/gateway/1.13/gateway-architecture-uc2)

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