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

# FTP Receive Endpoint Settings

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

FTP receive endpoints determine where to receive B2B messages transmitted over FTP. There are two
types of FTP endpoints:

- Receive from Partners

  Source endpoint in an inbound message flow that receives B2B messages from partners either
  directly or via third-party connections.

  A host, partner, or third-party connection can own FTP Receive from Partners endpoints.

- Source at Host

  Source endpoint in an outbound message flow that receives messages from the backend applications.

  Only a host can own FTP Source at Host endpoints.

Create FTP receive 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>Receive from partners</code> or <code>Source 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 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>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 server.</p></td><td><p>x</p></td></tr><tr><td><p>Character encoding override</p></td><td><p>Enables inbound endpoints to receive non UTF-8 encoded documents.</p></td><td></td></tr><tr><td><p>Username</p></td><td><p>Username for connecting to the FTP server.</p></td><td><p>x (if the server is authenticated)</p></td></tr><tr><td><p>Password</p></td><td><p>Password for the FTP server.</p></td><td><p>x (if the server is authenticated)</p></td></tr><tr><td><p>Source path</p></td><td><p>Path on the FTP server to which the partner or third-party connection sends the inbound files.</p></td><td><p>x</p></td></tr><tr><td><p>Skip Delete</p></td><td><div><div><p>When enabled, Partner Manager keeps the source file after reading and processing.</p></div><div><div data-type="NOTE">Use this configuration only when connecting to SFTP/FTP hosts that don’t allow explicit file deletion after the first read. Using this configuration with other SFTP/FTP hosts can result in duplicate file processing.</div></div></div></td><td></td></tr><tr><td><p>Skip empty files</p></td><td><p>Skip empty files during processing.</p></td><td><p>No</p></td></tr><tr><td><p>Polling Frequency</p></td><td><p>Frequency with which the server checks the source path for new files. The default is <code>1 minute</code>.</p></td><td><p>x</p></td></tr><tr><td><p>Supported Format Type</p></td><td><p>Applies only to FTP endpoints owned by partners or third-party connections. Indicates whether the endpoint supports EDI messages (EDIFACT, X12) or non-EDI messages (JSON, XML).</p></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. Only shows if the supported format type is non-EDI.</p></td><td><p>No</p></td></tr><tr><td><p>Size check wait time</p></td><td><p>Wait time, in seconds, between size checks to determine if a file is ready for processing. The default of <code>1 second</code> enables a file write to finish before processing the file.<br><br>Mule performs two size checks by waiting the amount of time specified in this field. If both checks return the same value, the file is ready to process.<br><br>To disable this feature, specify a negative number or omit the value.</p></td><td><p>x</p></td></tr><tr><td><p>Associated message type</p></td><td><p>(Applies when the format type is non-EDI) Message type to associate with the endpoint. If you select a message type, Partner Manager routes files received via the endpoint based on the selected message type instead of the filename.</p></td><td></td></tr><tr><td><p>Associated reference identifier</p></td><td><p>(Applies to partner and third-party endpoints when the format type is non-EDI) Partner information, such as the partner ID or third-party ID.</p></td><td></td></tr><tr><td><p>File name pattern</p></td><td><p>Filename pattern required by your partner.</p></td><td></td></tr><tr><td><p>Archival Path</p></td><td><div><div><p>FTP server path at which to store a copy of the file obtained from the source path.</p></div><div><div data-type="NOTE">The runtime application attempts to create the archive file up to three times. If permission or connection errors prevent Partner Manager from deleting the file, Partner Manager logs the issue in the runtime application and skips the archival step to prevent duplicate message processing.</div></div></div></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)
