All FTP access is closely monitored and provisioned through network firewall resources. Before you can take advantage of this interface you must coordinate with the support team to receive your access credentials. Provide at least one static IP address that represents the system you will use to send files via FTP. For systems using version 8.4 or later, you also have the option of using SFTP, Currently, both FTP and SFTP (also known as SSH File Transfer Protocol or Secure FTP) are supported.

To maintain security, FTP access is write-only—files in the directory cannot be read once they are uploaded to the FTP server. Directory scanning and reading are disabled, you can only deposit files to be processed. When you login to access the FTP server, you will not see any directories. If you have clients who you grant access to the FTP server, they cannot access one another's data, they can only write data to their own realms.

The FTP API resource will only allow connections from specified IP addresses. If you are not sure what your static IP is, ask your IT organization.

Which Data Delivery Technology is right for you?

  • SFTP – This is the file transfer technology used in the secure shell (SSH) application. It is widely used and is supported by many popular FTP clients.  All data is encrypted automatically in transit to the servers and this is the preferred delivery mechanism. 
  • FTP – Plain FTP is the other way to send your files to the servers.  It does not, however, offer any encryption and is therefore not the preferred method of delivery.  If you wish to use this method, you must provide written notice that you understand the risks posed by not using encryption to deliver your data.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk