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

# FTP Send Endpoint Settings

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

FTP send endpoint settings configure where to send B2B messages transmitted over FTP. There are two
types of FTP 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 FTP Send to Partners endpoints.

- Target at Host

  Target endpoint in an inbound message flow through which transformed B2B messages are sent to the
  backend applications

  Only a host can own FTP Target at Host endpoints.

Create FTP 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>FTP</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>FTP server host, such as <code>ftp.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 FTP.</p></td><td><p>x</p></td></tr><tr><td><p>Username</p></td><td><p>Username for the FTP server.</p></td><td><p>x</p></td></tr><tr><td><p>Password</p></td><td><p>Password for the FTP server.</p></td><td><p>x</p></td></tr><tr><td><p>Target Path</p></td><td><p>Path on your FTP server to EDI files that were generated from outbound message flows. This is also the path on your FTP server for storing transformed JSON and XML files generated from inbound message flows.</p></td><td><p>x</p></td></tr><tr><td><p>File name 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)