EMI Module - API & Integration Guide

1. How to Read / Quick Metadata

• Module: EMI
• Admin auth: JwtAuthGuard + RoleGuard + @Permissions(...)
• Mobile/customer auth: @Public()
• Admin base path: /api/admin/emi
• Mobile base path: /api/mobile/emi
• Success envelope: ResponseDto<T>

2. Route Summary

2.1 Admin

2.2 Mobile

3. Request / Response Shapes

3.1 Update config

• PUT /api/admin/emi/config
• Request body:

{
  "isEnabled": true,
  "periods": [3, 6, 12, 24]
}

3.2 Create bank

• POST /api/admin/emi/banks
• Request body:

{
  "name": "NMB Bank",
  "logoUrl": "https://example.com/logos/nmb-bank.png",
  "displayOrder": 1
}

3.3 Submit inquiry

• POST /api/mobile/emi/inquiries
• Request body:

{
  "productId": 42,
  "customerName": "John Doe",
  "customerEmail": "john@example.com",
  "customerMobile": "+9779800000000",
  "bankIds": [1, 3],
  "hasCreditCard": true,
  "downPaymentAmount": 500000,
  "message": "I prefer a 12-month option."
}

• Success response data:

{
  "id": 7
}

4. Error Reference

5. Integration Notes

• Mobile EMI config and bank endpoints are cache-backed.
• Inquiry writes snapshot the product title and sp value at submission time.
• Admin can deactivate banks without deleting historical inquiry links.