...
Transfer Method refers to how you wish to receive the extracted information.
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
We prefer the sending postback files via SFTP or HTTP POST over TLS (https) |
Here are the methods we support
| Table of Contents |
|---|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
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:
Username/password (Password must comply with these rules Transfer Method - Passwords )
SSH (key based authentication)
...
Pros | Cons |
|---|---|
|
|
|
Methods
Details Required
Host
Port
Username
Password
IPs used to connect to be added to the allow-lilst
Our environment will save the private key provided by your SFTP server in the initial login and use it in subsequent authentications.
...
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 |
|---|---|
| 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 |
|---|---|
|
|
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 |
|---|---|
|
|
Details Required
Email address