Customer routes
| Method | Route | Input | Response |
|---|---|---|---|
GET | /api/Customer/get-customer-by-email | email query parameter | Customer object |
GET | /api/Customer/get-customer-by-id/{customerId} | Route parameter | Customer object |
Customers, communication, lookup, and invoice-customer endpoints
These routes support surrounding integration tasks such as customer lookup, communication history, reference data, and invoice-customer actions.
Communication routes
| Method | Route | Input | Response |
|---|---|---|---|
GET | /api/Communication/get-all-messages/{applicationId} | skip, take query parameters | List of Message |
POST | /api/Communication/post-messages/{applicationId} | CommunicationRequest | bool |
post-messages requires non-empty contents.
user is required and limited to 30 characters.
get-all-messages is capped to 200 records per call.
Lookup and invoice-customer routes
| Method | Route | Input | Response |
|---|---|---|---|
GET | /api/Lookup/get-industries | None | Industry list |
GET | /api/InvoiceCustomer/get-invoice-customer/{loanId} | skip, take | Invoice customer list |
POST | /api/InvoiceCustomer/request-enable/{loanId} | invoiceCustomerId query parameter | bool |
Not covered as consumer help
TestingController is intentionally left out of the public help experience because it appears operational or test-focused.
PartnerController routes exist, but the current portal documentation focuses on partner integration flows rather than every internal reporting endpoint.