SFTP JSON Middleware for TMS
Budget / SalaryC$750–1,500
TypeFreelance project
LocationRemote
Posted1 hour ago
I need a reliable middleware that acts as the bridge between my Transport Management System (TMS) and an end customer who can only exchange data through an SFTP drop-box. The flow is two-way:
• From the customer to me: JSON files containing new orders and booking requests arrive in a watched SFTP folder. The service should fetch each file, transform or map the data to my TMS’s REST endpoints, push it in, and archive the original payload for audit.
• From me to the customer: once freight is moving, my TMS exposes shipment status, tracking updates, proof-of-delivery details, and invoice information. Your middleware must gather that data, package it into the customer’s required JSON schema, and place it back onto their SFTP in the correct outbound directory so they can ingest it.
Key points to cover:
– Set up middleware from scratch or rebuild as necessary due to lack of prior backups (only three JSON files provided by previous freelancer).
– Polling or event trigger for SFTP transfers (OpenSSH, WinSCP, or similar libraries are fine).
– Clean JSON mapping layer: field mapping table, error handling, and retry logic if a transfer or API call fails.
– Clear logging (preferably to a lightweight SQL or log file) so we can trace every transaction.
– Configuration via simple settings file or environment variables—no hard-coding of credentials.
– Unit tests plus a short test plan proving that:
1. An order file is picked up and reaches the TMS successfully.
2. A status update generated by the TMS lands on the customer’s SFTP in the proper format.
Deliverables:
1. Source code for the middleware (Python, Node.js, or .NET—use what you are fastest with).
2. Mapping documentation (JSON samples in ⇄ JSON samples out).
3. Deployment guide for a Windows or Linux VM.
4. Brief video or screen share demo walking through one complete cycle.
If you have handled JSON-over-SFTP integrations for logistics, I will value that experience. Let me know what tech stack you propose and an outline of your timeline, and I will get test credentials to you right away.
• From the customer to me: JSON files containing new orders and booking requests arrive in a watched SFTP folder. The service should fetch each file, transform or map the data to my TMS’s REST endpoints, push it in, and archive the original payload for audit.
• From me to the customer: once freight is moving, my TMS exposes shipment status, tracking updates, proof-of-delivery details, and invoice information. Your middleware must gather that data, package it into the customer’s required JSON schema, and place it back onto their SFTP in the correct outbound directory so they can ingest it.
Key points to cover:
– Set up middleware from scratch or rebuild as necessary due to lack of prior backups (only three JSON files provided by previous freelancer).
– Polling or event trigger for SFTP transfers (OpenSSH, WinSCP, or similar libraries are fine).
– Clean JSON mapping layer: field mapping table, error handling, and retry logic if a transfer or API call fails.
– Clear logging (preferably to a lightweight SQL or log file) so we can trace every transaction.
– Configuration via simple settings file or environment variables—no hard-coding of credentials.
– Unit tests plus a short test plan proving that:
1. An order file is picked up and reaches the TMS successfully.
2. A status update generated by the TMS lands on the customer’s SFTP in the proper format.
Deliverables:
1. Source code for the middleware (Python, Node.js, or .NET—use what you are fastest with).
2. Mapping documentation (JSON samples in ⇄ JSON samples out).
3. Deployment guide for a Windows or Linux VM.
4. Brief video or screen share demo walking through one complete cycle.
If you have handled JSON-over-SFTP integrations for logistics, I will value that experience. Let me know what tech stack you propose and an outline of your timeline, and I will get test credentials to you right away.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.