Multi-Lender Lead Routing Backend
Budget: ₹12,500 – ₹17,500 INR
The WordPress marketing site that collects loan enquiries is finished; what I now need is the engine that sits behind it. Your mission is to take each form submission, evaluate it against a set of routing rules, and fire it off—via REST—to one (or several) lender partners, then surface the results inside the existing WordPress admin as a lightweight CRM.
Core objectives
• Build a reusable backend module in PHP (WordPress-native), though I’m open to Node.js or Python if there is a clear technical advantage.
• Create and document integrations for multiple lender APIs (JSON/REST, OAuth or key-based). Each lender returns different field structures, so normalisation and robust error handling are essential.
• Develop a rules-driven router: think loan amount, credit score, geography and any future attributes I add. Rules must be editable from the WP dashboard without code changes.
• Queue asynchronous calls so the user sees an instant confirmation even when partner APIs are slow; MySQL will store both the raw lead and every partner response.
• Extend the current WP admin into a mini-CRM: searchable lead table, status tags (sent / accepted / declined), notes field, and export to CSV.
• Provide clean, commented source, Postman collections for each endpoint, and a short README so my in-house team can maintain it.
Acceptance criteria
1. A submitted lead reaches at least two sandbox lenders and logs a success status in WordPress.
2. Switching a rule on/off in the dashboard immediately changes routing behaviour without deployment.
3. No API call blocks the main thread; Lighthouse shows sub-200 ms server response to the user.
If you’ve built API-heavy, rules-based distribution systems before and can speak WordPress fluently, let’s talk.
Core objectives
• Build a reusable backend module in PHP (WordPress-native), though I’m open to Node.js or Python if there is a clear technical advantage.
• Create and document integrations for multiple lender APIs (JSON/REST, OAuth or key-based). Each lender returns different field structures, so normalisation and robust error handling are essential.
• Develop a rules-driven router: think loan amount, credit score, geography and any future attributes I add. Rules must be editable from the WP dashboard without code changes.
• Queue asynchronous calls so the user sees an instant confirmation even when partner APIs are slow; MySQL will store both the raw lead and every partner response.
• Extend the current WP admin into a mini-CRM: searchable lead table, status tags (sent / accepted / declined), notes field, and export to CSV.
• Provide clean, commented source, Postman collections for each endpoint, and a short README so my in-house team can maintain it.
Acceptance criteria
1. A submitted lead reaches at least two sandbox lenders and logs a success status in WordPress.
2. Switching a rule on/off in the dashboard immediately changes routing behaviour without deployment.
3. No API call blocks the main thread; Lighthouse shows sub-200 ms server response to the user.
If you’ve built API-heavy, rules-based distribution systems before and can speak WordPress fluently, let’s talk.