---
schema_version: "1"
id: 9f7d834e4fb68abd52889c3df6f0f85e2c2e5f66ad3859c506f7eec0fff919bf
title: Endpoints
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/endpoints.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/endpoints
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 572963e17ff2b8f71c73e4b643c23e1d6d8ade4fb4776c49dda8bdfbc4a23031
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# Endpoints

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

Endpoints define the transport protocol configurations necessary to receive or send messages with
external partners or internal backend applications.

Anypoint Partner Manager uses endpoints to:

- Receive messages from partners

- Receive messages from backend applications

- Define transport protocols

- Specify message or message acknowledgment destinations

## Endpoint Ownership

Depending on the endpoint type, you can assign the host, partner, or third-party connection as the
endpoint owner to control the use of endpoints within inbound and outbound message flows.

When creating partner-facing endpoints directly from a partner or third-party connection, the
ownership of the endpoint is automatically assigned to the entity from which the endpoint was
created.

In a message flow, endpoint availability depends on the endpoint ownership:

- If an endpoint is owned by the host, any partner or third-party connection can select the
  endpoint.

- If an endpoint is owned by a specific partner or third-party connection, then that endpoint is
  available only to the partner or third-party connection to which the endpoint is assigned.

## Supported Endpoint Protocols

The configuration of Partner Manager endpoints depends on the endpoint type and protocol. The
following table describes the endpoint types, along with their supported protocols and possible
owners:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Endpoint Type</th><th>Protocol</th><th>Owner</th></tr></thead><tbody><tr><td><p>Source at Host</p></td><td><p>FTP, HTTP, HTTPS, SFTP</p></td><td><p>Host</p></td></tr><tr><td><p>Target at Host</p></td><td><p>FTP, HTTP, HTTPS, SFTP</p></td><td><p>Host</p></td></tr><tr><td><p>Receive from Partners</p></td><td><p>AS2</p></td><td><p>Host</p></td></tr><tr><td></td><td><p>FTP, HTTP, HTTPS, SFTP</p></td><td><p>Host, partner, third-party connection</p></td></tr><tr><td><p>Send to Partners</p></td><td><p>AS2</p></td><td><p>Partner, third-party connection</p></td></tr><tr><td></td><td><p>FTP, HTTP, HTTPS, SFTP</p></td><td><p>Host, partner, third-party connection</p></td></tr></tbody></table>

## Endpoint Runtime Services

Using dynamic configurations, Partner Manager deploys generic endpoint services that can receive
data from or send data to different endpoint configurations. You can reuse the endpoint
configurations of all supported protocols across various message flows and partners.

Partner Manager’s deployment orchestration service inspects the message flow and associated
configuration objects and determines which endpoint services to deploy or update based on whether
any new endpoint configurations are added, updated, or removed.

The number and type of endpoint services deployed to your runtime depend on the transport protocols
used to exchange data with your partners and backend systems.

Each unique AS2, HTTP, and HTTPS receive endpoint configuration results in the deployment of its own
runtime application. You can view the runtime application name corresponding to a given
configuration in Partner Manager, from the endpoint details page.

The endpoints for the transport protocols are always managed within a single generic endpoint
service for the protocol and direction. The following table shows the prefix for the endpoint
services:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Protocol</th><th>Direction</th><th>Application Name Prefix</th></tr></thead><tbody><tr><td><p>AS2</p></td><td><p>Receive</p></td><td><p>b2b-inbound-as2-</p></td></tr><tr><td><p>AS2</p></td><td><p>Send</p></td><td><p>b2b-outbound-as2-</p></td></tr><tr><td><p>FTP</p></td><td><p>Receive</p></td><td><p>b2b-inbound-ftp-</p></td></tr><tr><td><p>FTP</p></td><td><p>Send</p></td><td><p>b2b-outbound-ftp-</p></td></tr><tr><td><p>HTTP or HTTPS</p></td><td><p>Receive</p></td><td><p>b2b-inbound-http-</p></td></tr><tr><td><p>HTTP or HTTPS</p></td><td><p>Send</p></td><td><p>b2b-outbound-http-</p></td></tr><tr><td><p>SFTP</p></td><td><p>Receive</p></td><td><p>b2b-inbound-sftp-</p></td></tr><tr><td><p>SFTP</p></td><td><p>Send</p></td><td><p>b2b-outbound-sftp-</p></td></tr></tbody></table>

If you deploy to CloudHub, you can assign static IP addresses to the endpoint applications that
connect to external systems from Runtime Manager, if your organization or your partners require
allowlisting IP addresses. You can share the
[static IP](https://docs.mulesoft.com/cloudhub/managing-applications-on-cloudhub#static-ips) address assigned to your
endpoint application with your partners for them to allowlist the IP address, allowing the
application to connect with their server.

## See Also

- [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint)

- [Deploying AS2, HTTP, and HTTPS Receive Endpoints](https://docs.mulesoft.com/partner-manager/latest/deploying-receive-endpoints)