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

# AS2 Send Endpoint Settings

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

AS2 send endpoint settings determine where to send B2B messages transmitted over AS2.

An AS2 Send to Partners endpoint (the only type of AS2 send endpoint) can act as:

- A target endpoint in an outbound message flow through which transformed B2B messages are sent to
  partners, either directly or via third-party connections

- An acknowledgment endpoint in an inbound message flow

Either a partner or a third-party connection can own AS2 send endpoints.

Create AS2 endpoints by configuring these settings on the partner or third-party connection pages:

<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>Partner or third-party connection that owns the endpoint.</p></td><td><p>x</p></td></tr><tr><td><p>Usage</p></td><td><p>Endpoint function (<code>Send to 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 subsequently 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>&lt;Host&gt; AS2 identifier</p></td><td><p>Your organization’s AS2 identifier.</p></td><td><p>x</p></td></tr><tr><td><p>&lt;Partner&gt; AS2 identifier</p></td><td><p>Your partner’s AS2 identifier, which appears if the endpoint is used to send transactions directly to a partner without going through a third-party connection.</p></td><td><p>x</p></td></tr><tr><td><p>&lt;VAN&gt; AS2 identifier</p></td><td><p>Your VAN’s AS2 identifier, which appears if the endpoint is used to send transactions to a third-party connection.</p></td><td><p>x</p></td></tr><tr><td><p>Partner AS2 URL</p></td><td><p>Your partner’s or third-party connection’s AS2 URL to which outbound EDI transmissions are sent.</p></td><td><p>x</p></td></tr><tr><td><p>Certificate (TLS context)</p></td><td><div><div><p>(Applies when the <strong>Partner AS2 URL</strong> field starts with <code>https</code>) SSL certificate. Values are:</p></div><div><ul><li><p><code>Use CA-signed certificates</code></p><div><p>Uses a certificate that was issued and signed by a certificate authority (CA). With this option, you don’t need to upload an additional certificate.</p></div></li><li><p><code>Use a self-signed certificate</code></p><div><p>Uses a certificate that was not issued or signed by a CA. With this option, you must either select an existing certificate or upload a new certificate in <code>.pem</code> format.</p></div></li><li><p><code>Allow insecure connection</code></p><div><p>Allows an insecure connection that doesn’t perform certificate validation.</p></div><div><p>Don’t use this option in production environments. Use it only during testing.</p></div></li></ul></div></div></td><td><p>x<a id="transfer-mode"></a></p></td></tr><tr><td><p>Transfer Mode</p></td><td><div><div><p>The transfer mode applied when sending AS2 transmissions. Values are:</p></div><div><ul><li><p><strong>Auto</strong></p><div><p>Selected by default.</p></div></li><li><p><strong>Chunked Transfer Mode</strong></p><div><p>Always streaming.</p></div></li><li><p><strong>Identity Transfer Mode</strong></p><div><p>Never streaming.</p></div></li></ul></div></div></td><td><p>x</p></td></tr><tr><td><p>Connection timeout</p></td><td><p>Timeout for establishing a connection to the remote service. The default is <code>30 Seconds</code>.</p></td><td><p>x</p></td></tr><tr><td><p>Retry interval</p></td><td><p>Frequency of reconnection attempts when unable to connect to the remote AS2 service. The default is <code>30 Seconds</code>.</p></td><td><p>x</p></td></tr><tr><td><p>Maximum retry attempts</p></td><td><p>Maximum number of reconnection attempts to make. If you don’t want Partner Manager to retry after an initial connection failure, set this value to <code>0</code>.</p></td><td><p>x</p></td></tr><tr><td><p>Respond to email address</p></td><td><p>Email address to use as the HTTP <code>From</code> header when sending.</p></td><td><p>x</p></td></tr><tr><td><p>Message subject</p></td><td><p>User-defined field for the MIME Subject header.</p></td><td><p>x</p></td></tr><tr><td><p>Filename pattern</p></td><td><p>Filename pattern required by your partner.</p></td><td><p>x</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. To create a new keystore when creating an endpoint:</p></div><div><div><div><ol><li><p>Click <strong>New</strong>.</p></li><li><p>Complete the fields on the <strong>New keystore for &lt;host&gt; window</strong>.</p></li><li><p>Click <strong>Upload Keystore</strong>.</p></li></ol></div></div></div><div><p>For more information about host keystores, see <a href="https://docs.mulesoft.com/partner-manager/latest/manage-as2-host-keystores">Managing AS2 Host Keystores</a>.</p></div></div></td><td></td></tr><tr><td><p>Encryption algorithm</p></td><td><p>Algorithm to use when encrypting the message to send.</p></td><td><p>x</p></td></tr><tr><td><p>Signature algorithm</p></td><td><p>Algorithm to use when setting the message-integrity check value.</p></td><td><p>x</p></td></tr><tr><td><p>Request receipt</p></td><td><div><div><p>Whether you want the partner to return a Message Disposition Notification (MDN) receipt.</p></div></div></td><td><p>x</p></td></tr><tr><td><p>MDN response</p></td><td><p>The AS2 messages sent from Partner Manager always request the receiver to send a Synchronous MDN receipt back. This value is always set to <code>Sync</code>.</p></td><td><p>x</p></td></tr><tr><td><p>MDN signature algorithm</p></td><td><p>Request for a partner to respond with a signed Message Disposition Notification (MDN) using this algorithm for calculating the Message Integrity Check (MIC).</p></td><td><p>x</p></td></tr></tbody></table>

## See Also

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

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

- [Filename Patterns for Send Endpoints](https://docs.mulesoft.com/partner-manager/latest/file-name-pattern)

- [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)