REST Supplier-Store API Bridge
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted1 hour ago
I need a reliable, fully-automated bridge that sits between my supplier’s REST API and my online store’s REST API. The aim is to remove every manual touchpoint, so products, prices, stock levels and digital-key orders flow on their own.
Here is the workflow I want to see running end-to-end:
• Product side
The bridge pulls the full product catalogue from the supplier, stores it locally, then pushes mapped items, prices and inventory to my store. Mapping must be preserved so future updates keep everything aligned.
• Order side
When a customer places an order, the bridge catches it instantly, calls the supplier API to purchase the corresponding digital key, retrieves the key and posts it straight back through the store API so the customer receives it without delay.
Technical notes
– Both APIs are REST.
– A small, fast database (SQL or NoSQL is fine) should sit in the middle for caching, mapping and deduplication.
– On any failed call the bridge should automatically retry with exponential back-off; I’ll review other alerting/logging options later, but solid retry logic is essential from day one.
– Idempotency is critical so duplicate orders never slip through.
– Clean code, clear config files and concise README are expected so I can re-deploy or hand it to another dev easily.
Deliverables
1. Source code and deployment script (Docker preferred).
2. Database schema or migration file.
3. Postman or cURL collection that demonstrates each endpoint in both directions.
4. A brief test report showing successful product sync and a complete order-to-delivery cycle with retries simulated.
If you have experience building similar two-way API syncs for e-commerce or gaming key stores, this should be straightforward and quick to prove. I’m ready to start as soon as you can outline your proposed stack and timeline.
Here is the workflow I want to see running end-to-end:
• Product side
The bridge pulls the full product catalogue from the supplier, stores it locally, then pushes mapped items, prices and inventory to my store. Mapping must be preserved so future updates keep everything aligned.
• Order side
When a customer places an order, the bridge catches it instantly, calls the supplier API to purchase the corresponding digital key, retrieves the key and posts it straight back through the store API so the customer receives it without delay.
Technical notes
– Both APIs are REST.
– A small, fast database (SQL or NoSQL is fine) should sit in the middle for caching, mapping and deduplication.
– On any failed call the bridge should automatically retry with exponential back-off; I’ll review other alerting/logging options later, but solid retry logic is essential from day one.
– Idempotency is critical so duplicate orders never slip through.
– Clean code, clear config files and concise README are expected so I can re-deploy or hand it to another dev easily.
Deliverables
1. Source code and deployment script (Docker preferred).
2. Database schema or migration file.
3. Postman or cURL collection that demonstrates each endpoint in both directions.
4. A brief test report showing successful product sync and a complete order-to-delivery cycle with retries simulated.
If you have experience building similar two-way API syncs for e-commerce or gaming key stores, this should be straightforward and quick to prove. I’m ready to start as soon as you can outline your proposed stack and timeline.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.