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

# SFTP Send Endpoint Settings

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

SFTP send endpoint settings configure where to send B2B messages transmitted over SFTP. There are
two types of SFTP send endpoints:

- Send to Partners

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

  - Acknowledgement endpoint in an inbound message flow

  A host, partner, or third-party connection can own SFTP Send to Partners endpoints.

- Target at Host

  Target endpoint in an inbound message flow through which transformed JSON and XML messages are
  sent to the backend applications.

  Only a host can own SFTP Target at Host endpoints.

Create SFTP send endpoints by configuring these settings on the **<host>** or **<partner>** pages.
You can also create these endpoints when you configure an outbound message flow:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Name</th><th>Description</th><th>Required</th></tr></thead><tbody><tr><td><p>Owner</p></td><td><p>Host, 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> or <code>Target at host</code>).</p></td><td><p>x</p></td></tr><tr><td><p>Protocol</p></td><td><p>Protocol that the endpoint supports (<code>SFTP</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>Retry interval (in seconds)</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>No</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>No</p></td></tr><tr><td><p>Host</p></td><td><p>SFTP server host, such as <code>sftp.mulesoft.com</code>, <code>localhost</code>, or <code>192.168.0.1</code>. The host must be accessible from your Mule environment.</p></td><td><p>x</p></td></tr><tr><td><p>Port</p></td><td><p>Port number of the SFTP.</p></td><td><p>x</p></td></tr><tr><td><p>Authentication type</p></td><td><div><div><p>Authentication method used to secure the SFTP endpoint. Values are:</p></div><div><ul><li><p><strong>None</strong></p><div><p>Provides no authentication for the endpoint</p></div></li><li><p><strong>Basic</strong></p><div><p>Authenticates by using a username and password</p></div></li><li><p><strong>Identity Key</strong></p><div><p>Authenticates by using a private SSH identity key</p></div></li><li><p><strong>Basic and Identity Key</strong></p><div><p>Authenticates by using a username, password, and public SSH identity key</p></div></li></ul></div></div></td><td><p>x</p></td></tr><tr><td><p>Username</p></td><td><p>(Applies to all authentication types except <code>None</code>)</p><p>Username for the SFTP server.</p></td><td><p>x</p></td></tr><tr><td><p>Password</p></td><td><p>(Applies to these authentication types: <code>Basic</code>, <code>Basic and Identity Key</code>)</p><p>Password for the SFTP server.</p></td><td><p>x</p></td></tr><tr><td><p>SSH</p></td><td><div><div><p>(Applies to these authentication types: <code>Identity Key</code>, <code>Basic and Identity Key</code>)</p></div><div><p>SSH private key file. The following considerations apply:</p></div><div><ul><li><p>Send and receive endpoints that have the same owner can use the same SSH private key file.</p></li><li><p>Multiple message flows for the same or different partners can reference endpoints that use the same SSH private key file.</p></li></ul></div><div><p>You can either select a private key file (<code>.pem</code>) that’s already configured in Anypoint Partner Manager or create a new configuration for a private key file.</p></div><div><p>To create a new configuration for a private key file:</p></div><div><ol><li><p>In the <strong>&lt;partner&gt; SSH</strong> or <strong>&lt;host&gt; SSH</strong> field, click <strong>Select</strong>.</p></li><li><p>In the <strong>Select a &lt;partner&gt; ssh</strong> or <strong>Select a &lt;host&gt; ssh</strong> dialog, click <strong>New</strong>.</p></li><li><p>Complete the fields in the <strong>New certificate for &lt;partner&gt;</strong> or <strong>New certificate for &lt;host&gt;</strong> dialog:</p><div><ul><li><p><strong>Identity Key name</strong></p><div><p>Enter the name of the private key file.</p></div></li><li><p><strong>&lt;partner&gt; identity key PEM file</strong> or <strong>&lt;host&gt; identity key PEM file</strong></p><div><p>Click <strong>Choose file</strong> to select the private key file.</p></div></li><li><p><strong>Key passphrase</strong></p><div><p>Enter the passphrase for the private key file.</p></div></li><li><p><strong>Expiration date</strong></p><div><p>Enter the date on which you want the private key file to expire. This date is a reminder for you, but Anypoint Partner Manager doesn’t enforce it.</p></div></li></ul></div></li><li><p>Click <strong>Create</strong>.</p></li></ol></div></div></td><td><p>x</p></td></tr><tr><td><p>Target Path</p></td><td><p>Path on your SFTP server to EDI files that were generated from outbound message flows. This is also the path on your SFTP server for storing transformed JSON and XML files generated from inbound message flows.</p></td><td><p>x</p></td></tr><tr><td><p>Filename pattern</p></td><td><p>Filename pattern required by your partner or back-end application.</p></td><td></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)