Postback - Transfer Method

Owned by rossc
Last updated: Apr 04, 2024 by rossc
1 min read

Transfer Method refers to how you wish to receive the extracted information.

We prefer the sending postback files via SFTP or HTTP POST over TLS (https)

 

Here are the methods we support

 

Passwords and Authentication Tokens must not be provided in plain text. Please use a tool like pwpush.com

 

SFTP

Two types of SFTP is supported:

Pros

Cons

Pros

Cons

  • Best for your ERP/WMS to receive the files in your environment

  • Reliable transfer

  • Encrypted files

  • Authenticated transfer

  • Hosting of SFTP server

Details Required

  • Host

  • Port

  • Username

  • Password or Public key of the server

  • Allow list our outgoing SFTP server IP Allowlisting EFM URLs & IP Addresses

  • Provide the fingerprint of the public key, as we use that to validate that we are connecting to the correct server.

HTTP POST

We can send XML data to an API endpoint but it is a one way transaction of data, we do not match and find references to reconcile the consignment details to.

Pros

Cons

Pros

Cons

  • Secure transmission of file

  • Reliable transfer

Must be able to configure an authenticated API client

Details Required

  • HTTPS Endpoint only

  • EFM specific authentication (ie no unauthenticated endpoints)

FTP (TLS ONLY if SFTP is not an option)

Pros

Cons

Pros

Cons

  • Suitable if you cannot setup an SFTP server or HTTP POST

  • When certificate changes, failures in transmission can occur

  • Unforseen errors can cause files to fail to send

Details Required

  • Host

  • Username

  • Password

  • Port

Email - Legacy

We are able to send postback files to email addresses. Please see Postback - Email (Legacy Option) for more details.

Pros

Cons

Pros

Cons

  • Suitable if you cannot setup an SFTP server

  • We cannot validate delivery of the file

  • If a receiver of the report leaves your organisation, the mail may end up not being delivered.

Details Required

  • Email address