FTP VS API
FTP API
1. Client transfers stock file to UNI Server. 1. We fetch the Stock file from Clients Server.
2. UNI will share the FTP credentials and Endpoint link as 2. Client will share the Endpoint URL and Documentation
Vendor is connecting to our Server. as we are connecting to Clients Server.
3. Third Party FTP client (WinSCP / Filezilla) are needed to 3. No FTP client needed connect to Clients Server.
connect to UNI Server. Connection is done as per the clients documentation.
4. Automation is done via Windows Task Scheduler. Min 4. Automation is done directly depending on Client
interval is 30 mins. server settings. Min Interval is 15 mins.
Moving from FTP to API based uploads
1. Ask the client for the following:
• API Endpoint URL
• API documentation
• API access authentication credentials
2. Once you receive the requested details, email to Support.
3. Request for the FTP access to be discontinued and for API to be activated.
Moving from API to FTP based uploads
1. Get the FTP authentication credentials and UNI Server URL from Support.
2. Share the details received with the Vendor.
3. Vendor may have to download FTP client (WinSCP / Filezilla) to transfer the stock file to UNI Server.
4. Request Support for the API access to be discontinued and for FTP access to be activated.