---
schema_version: "1"
id: 7cdd1d3c4e3d4b6b86276d6eb3e264fbe22078c5f4a0af0665acc0cefa2d4d10
title: AS2 Receive Endpoint Settings
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/endpoint-as2-receive.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/endpoint-as2-receive
source_site: docs.mulesoft.com
content_type: documentation
content_hash: a1e9d50d87d6be9c75f87d6349828d155474c5935337053e39763f86fb9bafa2
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# AS2 Receive Endpoint Settings

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

AS2 receive endpoint settings determine where to receive B2B messages received over AS2.

An AS2 Receive from Partners endpoint (the only type of AS2 receive endpoint) acts as the source
endpoint in an inbound message flow that receives B2B messages from partners either directly or via
third-party connections. One AS2 endpoint can receive data from multiple partners, multiple
third-party connections, or both.

Only a host can own AS2 Receive from Partners endpoints.

> [!IMPORTANT] Each AS2 receive endpoint configuration gets deployed as an individual Mule
> application in the runtime. To minimize the number of vCores needed to run Anypoint Partner
> Manager, use an existing AS2 receive endpoint configuration across multiple message flows.

Create an AS2 Receive from Partners endpoint by configuring these settings on the **<host>** page:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Required</th></tr></thead><tbody><tr><td><p>Owner</p></td><td><p>Host that owns the endpoint.</p></td><td><p>x</p></td></tr><tr><td><p>Usage</p></td><td><p>Endpoint function (<code>Receive from partners</code>).</p></td><td><p>x</p></td></tr><tr><td><p>Protocol</p></td><td><p>Protocol that the endpoint supports (<code>AS2</code>).</p></td><td><p>x</p></td></tr><tr><td><p>Endpoint name</p></td><td><p>Automatically generated name used to identify the endpoint, which you can modify manually.</p></td><td><p>x</p></td></tr><tr><td><p>Description</p></td><td><p>User-supplied value that describes the purpose of the endpoint.</p></td><td></td></tr><tr><td><p>Private port (when deploying to VPC)</p></td><td><div><div><p>Applies when using Anypoint Virtual Private Cloud (Anypoint VPC) with CloudHub 1.0 deployments:</p></div><div><ul><li><p>When enabled, the AS2 receive endpoint application deploys to the private port <code>8092</code> in your <a href="https://docs.mulesoft.com/cloudhub/virtual-private-cloud">Anypoint VPC</a>. You can manage the access control to the endpoint via the Anypoint VPC and dedicated load balancer settings.</p></li><li><p>When disabled, the AS2 receive endpoint application deploys to the public port <code>8082</code> by default.</p><div><p>You can access the endpoint URL directly over the internet.</p></div></li></ul></div></div></td><td></td></tr><tr><td><p>HTTPS</p></td><td><div><div><p>Applies to CloudHub 1.0 deployments.</p></div><div><p>Indicates whether Partner Manager deploys the AS2 receive endpoint as an HTTPS listener:</p></div><div><ul><li><p>If enabled (default), Partner Manager deploys the AS2 receive endpoint as an HTTPS listener.</p></li><li><p>If disabled, Partner Manager deploys the AS2 receive endpoint as an HTTP listener.</p></li></ul></div><div><p>The <strong>HTTPS</strong> option is disabled when creating Receive from Partners endpoints in CloudHub 2.0.</p></div><div><div data-type="NOTE">When deploying to Anypoint Runtime Fabric, Partner Manager always deploys the AS2 receive endpoint as an HTTP listener. With this type of deployment, you must configure an Ingress controller to provide external consumers with an HTTPS endpoint. For more information, see <a href="https://docs.mulesoft.com/runtime-fabric/latest/custom-ingress-configuration">Configuring Ingress for Runtime Fabric</a>.</div></div><div><div data-type="NOTE"><div><p>When deploying to CloudHub 2.0, Partner Manager always deploys the AS2 Receive endpoint as an HTTPS listener.</p></div><div><ul><li><p>When using a shared space as a deployment target, HTTP requests aren’t allowed.</p></li><li><p>If you want to allow HTTP requests to the AS2 receive endpoint application:</p><div><ol><li><p>Use a private space as the deployment target.</p></li><li><p>On the <strong>Advanced</strong> tab, select <code>Accept HTTP</code> in the <strong>HTTP requests</strong> field.</p></li><li><p>Optionally, configure Network-Level Ingress Rules to allow HTTP requests from specific IP addresses.</p></li></ol></div></li></ul></div></div></div></div></td><td><p>x</p></td></tr><tr><td><p><a id="manage-api-manager"></a>Manage with API Manager</p></td><td><div><div><p>Allows you to manage the endpoint in API Manager, where you can apply policies, such as authentication and client credentials, and configure SLA tiers. Document your message specifications by using Exchange and share them with your partners via public portals from Exchange or by obtaining an additional license and sharing the specifications in API Experience Hub.</p></div><div><p>To manage an endpoint in API Manager, create an HTTP API in API Manager in the same environment and organization as the endpoint.</p></div><div><p>When you create the API in API Manager:</p></div><div><ul><li><p>Select <code>HTTP API</code> as the asset type.</p></li><li><p>Leave the defaults on the <strong>Endpoint configuration</strong> screen.</p></li><li><p>Copy the API instance ID and paste it into the <strong>API Auto discovery id</strong> field in the Partner Manager <strong>New endpoint: Receive from Partners</strong> window.</p></li></ul></div></div></td><td><p>x</p></td></tr><tr><td><p>Use hyphen (-) as the secondary file name delimiter to determine non-EDI message type</p></td><td><p>Lets you use a hyphen as the secondary file name delimiter to determine the message type from the message’s file name.</p></td><td><p>No</p></td></tr><tr><td><p>AS2 URL</p></td><td><p>URL to the AS2 server (automatically generated).</p></td><td><p>x</p></td></tr><tr><td><p>Enforce security level</p></td><td><div><div><p>Indicates whether Partner Manager rejects incoming AS2 messages that aren’t signed, encrypted, or both. When Partner Manager rejects a message, it returns a negative Message Disposition Notification (MDN) to the sender.</p></div><div><p>Allowed values:</p></div><div><ul><li><p><code>Signed &amp; Encrypted</code></p><div><p>(Default) Rejects incoming messages that aren’t both signed and encrypted.</p></div></li><li><p><code>Signed</code></p><div><p>Rejects incoming messages that aren’t signed.</p></div></li><li><p><code>Encrypted</code></p><div><p>Rejects incoming messages that aren’t encrypted.</p></div></li><li><p><code>None</code></p><div><p>Accepts messages that aren’t signed or encrypted.</p></div></li></ul></div><div><p>When deploying an AS2 endpoint to CloudHub using the HTTP protocol, you cannot change the default value (<code>Signed &amp; Encrypted</code>).</p></div></div></td><td><p>x</p></td></tr><tr><td><p>App Name Substitution Type</p></td><td><div><div><p>Defines how the ingress URL template <code>app-name</code> is substituted for this AS2 endpoint to generate the Runtime Fabric public endpoint.</p></div><div><ul><li><p>Select Default to use <code>app-name</code> as deployment-name.</p></li><li><p>Select Custom to provide a custom name for the <code>app-name</code> substitution.</p></li><li><p>Select BasePath to use the editable AS2 base path as the value for the <code>app-name</code> substitution.</p></li></ul></div></div></td><td><p>No</p></td></tr><tr><td><p>&lt;Host&gt; keystore</p></td><td><div><div><p>Host keystore file that stores your organization’s public certificate and private key. Select an existing keystore file or create a new one.</p></div><div><p>To create a new keystore file:</p></div><div><ol><li><p>In the <strong>&lt;host&gt; Keystore</strong> field, click <strong>Select</strong>.</p></li><li><p>Click <strong>New</strong>.</p></li><li><p>Complete the fields on the <strong>New certficate for &lt;host&gt; window</strong>, as described in <a href="https://docs.mulesoft.com/partner-manager/latest/manage-as2-host-keystores">Managing AS2 Host Keystores</a>.</p></li><li><p>Click <strong>Create</strong>.</p></li></ol></div></div></td><td><p>x</p></td></tr></tbody></table>

Follow these steps to add basic authentication for incoming AS2 messages from your partners:

1.  Configure the endpoint with [Manage with API Manager](#manage-api-manager).

2.  Configure a client credentials policy in API Manager and select **HTTP Basic Authentication
    Header** as the credentials origin.

    ![Configure client credentials policy in API Manager](/mulesoft/current/en-us/partner-manager/latest/_images/configure-client-credentials-policy.png)

3.  Add documentation to the HTTP API from Exchange and engage with your partners by publishing it
    to the [public portal](https://docs.mulesoft.com/exchange/to-share-api-asset-to-portal) from Exchange or via API
    Experience Hub.

    - If you publish via a portal, your partners must log in and request access.

    - If you follow the
      [API request process](https://docs.mulesoft.com/api-experience-hub/requesting-access-to-an-api-instance) on behalf
      of your partners, HTTP basic auth headers pass the client ID and client secret upon request.

## Next Step

After you create an AS2 receive endpoint, you can deploy it, as described in
[Deploying AS2, HTTP, and HTTPS Receive Endpoints](https://docs.mulesoft.com/partner-manager/latest/deploying-receive-endpoints).

## See Also

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

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

- [AS2 Signature and Encryption Algorithms](https://docs.mulesoft.com/partner-manager/latest/as2-endpoints-algorithms)

- [Managing Host Certificates](https://docs.mulesoft.com/partner-manager/latest/manage-host-certificates)