Enumerated Values Index
Complete reference for all enumerated values used in LendFoundry LOS and LMS APIs
Enumerated Values Index
Quick ReferenceThis document provides a comprehensive index of all enumerated values (enums) used throughout the LendFoundry API. Use this reference when constructing API requests to ensure you're using valid enum values.
Enumerated values are predefined constants that specify the allowed values for specific fields in API requests and responses. Using the correct enum values is essential for successful API integration.
Overview
What Are Enumerated Values?
Enumerated values (enums) are predefined constants that specify the exact string values allowed for specific fields in API requests and responses. They ensure data consistency and prevent invalid values from being submitted.
How to Use This Reference
- Find the enum type you need (e.g.,
ApplicationStatusValues,PaymentStatusValues) - Review the allowed values and their descriptions
- Use the exact string value in your API requests (case-sensitive)
- Check code examples for implementation patterns
Enum Value Format
All enum values are case-sensitive strings. Use the exact value as shown in the tables below:
{
"status": "Approved", // β
Correct
"status": "approved", // β Wrong (lowercase)
"status": "APPROVED" // β Wrong (uppercase)
}LOS Enumerated Values
The Loan Origination System (LOS) uses the following enumerated values for application and verification workflows.
Application Status Values
Application status values track the progress of a loan application through the origination process.
| Value | Description |
|---|---|
Submitted | Initial application submission |
Pending Approval | Application under review |
Offer Generated | Offer has been created for the borrower |
Pending Offer | Awaiting borrower acceptance of offer |
Approved | Application approved and ready for onboarding |
Rejected | Application rejected |
Not Interested | Borrower declined the offer |
Application Status Flow:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π Application Status Flow]
direction LR
A[π Submitted] --> B[β³ Pending Approval]
B --> C[π Offer Generated]
C --> D[β³ Pending Offer]
D --> E[β
Approved]
D --> F[β Rejected]
D --> G[π« Not Interested]
end
style A fill:#2563eb,stroke:#1e40af,color:#fff
style B fill:#d97706,stroke:#b45309,color:#fff
style C fill:#2563eb,stroke:#1e40af,color:#fff
style D fill:#d97706,stroke:#b45309,color:#fff
style E fill:#059669,stroke:#047857,color:#fff
style F fill:#dc2626,stroke:#b91c1c,color:#fff
style G fill:#6b7280,stroke:#4b5563,color:#fff
Verification Data Status Values
Verification data status values indicate the current state of document and data verification processes.
| Value | Description |
|---|---|
None | Verification not yet initiated |
Initiated | Verification process started |
Pending Doc | Document required from borrower |
InProgress | Document uploaded and under review |
Completed | Verification process complete |
Failed | Verification failed |
Verification Data Status Flow:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π Verification Data Status Flow]
direction LR
A[βͺ None] --> B[π Initiated]
B --> C[π Pending Doc]
C --> D[β³ InProgress]
D --> E[β
Completed]
D --> F[β Failed]
end
style A fill:#6b7280,stroke:#4b5563,color:#fff
style B fill:#2563eb,stroke:#1e40af,color:#fff
style C fill:#d97706,stroke:#b45309,color:#fff
style D fill:#d97706,stroke:#b45309,color:#fff
style E fill:#059669,stroke:#047857,color:#fff
style F fill:#dc2626,stroke:#b91c1c,color:#fff
Verification Result Values
Verification result values indicate the outcome of a verification process.
| Value | Description |
|---|---|
Passed | Verification successful |
Failed | Verification failed |
Review | Manual review required |
Verification Result Flow:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[βοΈ Verification Result]
direction LR
A{βοΈ Verification} --> B[β
Passed]
A --> C[β Failed]
A --> D[π Review]
end
style A fill:#6b7280,stroke:#4b5563,color:#fff
style B fill:#059669,stroke:#047857,color:#fff
style C fill:#dc2626,stroke:#b91c1c,color:#fff
style D fill:#d97706,stroke:#b45309,color:#fff
LMS Enumerated Values
The Loan Management System (LMS) uses the following enumerated values for loan servicing, payments, and transactions.
Loan Status Values
Loan status values indicate the current state of a loan in the servicing system.
| Value | Description |
|---|---|
Unfunded | Loan created but not yet funded |
Funded | Loan has been funded |
Active | Loan is active and in repayment |
Delinquent | Loan is past due |
Default | Loan is in default |
ChargedOff | Loan has been charged off |
PaidOff | Loan has been fully paid off |
Closed | Loan is closed |
Loan Status Flow:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π° Loan Status Flow]
direction LR
A[π Unfunded] --> B[π΅ Funded]
B --> C[β
Active]
C --> D[β οΈ Delinquent]
C --> E[β Default]
D --> E
E --> F[π ChargedOff]
C --> G[β
PaidOff]
G --> H[π Closed]
F --> H
end
style A fill:#6b7280,stroke:#4b5563,color:#fff
style B fill:#2563eb,stroke:#1e40af,color:#fff
style C fill:#059669,stroke:#047857,color:#fff
style D fill:#d97706,stroke:#b45309,color:#fff
style E fill:#dc2626,stroke:#b91c1c,color:#fff
style F fill:#dc2626,stroke:#b91c1c,color:#fff
style G fill:#059669,stroke:#047857,color:#fff
style H fill:#374151,stroke:#1f2937,color:#fff
Payment Status Values
Payment status values track the progress of payment transactions.
| Value | Description |
|---|---|
Initiated | Payment initiated by user or system |
Submitted | Payment submitted for processing |
Success | Payment successfully processed |
Failed | Payment processing failed |
Reversed | Payment reversed |
Cancelled | Payment cancelled |
Payment Status Flow:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π³ Payment Status Flow]
direction LR
A[π Initiated] --> B[π€ Submitted]
B --> C[β
Success]
B --> D[β Failed]
C --> E[β©οΈ Reversed]
B --> F[π« Cancelled]
end
style A fill:#2563eb,stroke:#1e40af,color:#fff
style B fill:#d97706,stroke:#b45309,color:#fff
style C fill:#059669,stroke:#047857,color:#fff
style D fill:#dc2626,stroke:#b91c1c,color:#fff
style E fill:#6b7280,stroke:#4b5563,color:#fff
style F fill:#6b7280,stroke:#4b5563,color:#fff
Payment Instrument Values
Payment instrument values specify the method used for payment.
| Value | Description |
|---|---|
Cash | Cash payment |
Check | Check payment |
ACH | ACH bank transfer |
DebitCard | Debit card payment |
Wire | Wire transfer |
Payment Instruments:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#6b7280', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π³ Payment Instruments]
direction LR
A[π΅ Cash] --- B[π Check] --- C[π¦ ACH] --- D[π³ DebitCard] --- E[π Wire]
end
style A fill:#2563eb,stroke:#1e40af,color:#fff
style B fill:#2563eb,stroke:#1e40af,color:#fff
style C fill:#2563eb,stroke:#1e40af,color:#fff
style D fill:#2563eb,stroke:#1e40af,color:#fff
style E fill:#2563eb,stroke:#1e40af,color:#fff
Payment Type Values
Payment type values specify how a payment should be allocated.
| Value | Description |
|---|---|
System | Use system default payment hierarchy |
Schedule | Apply to scheduled payment |
PrincipalOnly | Apply to principal only |
Payoff | Full loan payoff |
Custom | Custom payment allocation |
LOC Status Values
Line of Credit (LOC) status values indicate the current state of a credit line.
| Value | Description |
|---|---|
Active | LOC is active and available for draws |
Suspended | LOC temporarily disabled |
Closed | LOC fully closed |
Cancelled | LOC permanently cancelled |
LOC Status Flow:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π³ LOC Status Flow]
direction LR
A[β
Active] --> B[βΈοΈ Suspended]
A --> C[π Closed]
A --> D[π« Cancelled]
B --> C
end
style A fill:#059669,stroke:#047857,color:#fff
style B fill:#d97706,stroke:#b45309,color:#fff
style C fill:#374151,stroke:#1f2937,color:#fff
style D fill:#dc2626,stroke:#b91c1c,color:#fff
Draw Status Values
Draw status values track the progress of Line of Credit draw requests.
| Value | Description |
|---|---|
Requested | Draw requested by borrower |
Approved | Draw approved |
Rejected | Draw rejected |
Funded | Draw funded and disbursed |
Cancelled | Draw cancelled |
Draw Status Flow:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π Draw Status Flow]
direction LR
A[π Requested] --> B{βοΈ Decision}
B -->|β
| C[β
Approved]
B -->|β| D[β Rejected]
C --> E[π΅ Funded]
A --> F[π« Cancelled]
end
style A fill:#2563eb,stroke:#1e40af,color:#fff
style B fill:#6b7280,stroke:#4b5563,color:#fff
style C fill:#059669,stroke:#047857,color:#fff
style D fill:#dc2626,stroke:#b91c1c,color:#fff
style E fill:#059669,stroke:#047857,color:#fff
style F fill:#6b7280,stroke:#4b5563,color:#fff
Fee Type Values
Fee type values specify when and how fees are applied.
| Value | Description |
|---|---|
Scheduled | Fee applied on scheduled date |
PerOccurrence | Fee applied per event occurrence |
PreApplied | Fee applied upfront |
ChargeOff | Fee applied after charge-off |
Transaction Type Values
Transaction type values categorize financial transactions.
| Value | Description |
|---|---|
Payment | Payment transaction |
Fee | Fee transaction |
Interest | Interest accrual |
Principal | Principal change |
Waiver | Fee waiver |
Reversal | Transaction reversal |
Transaction Types:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#6b7280', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π³ Transaction Types]
direction LR
A[π³ Payment] --- B[π° Fee] --- C[π Interest] --- D[π΅ Principal] --- E[β
Waiver] --- F[β©οΈ Reversal]
end
style A fill:#2563eb,stroke:#1e40af,color:#fff
style B fill:#d97706,stroke:#b45309,color:#fff
style C fill:#2563eb,stroke:#1e40af,color:#fff
style D fill:#2563eb,stroke:#1e40af,color:#fff
style E fill:#059669,stroke:#047857,color:#fff
style F fill:#6b7280,stroke:#4b5563,color:#fff
Collection Status Values
Collection status values indicate the delinquency stage of a loan.
| Value | Description |
|---|---|
Current | Loan is current (not in collections) |
Early | Early delinquency (1-30 days past due) |
Late | Late delinquency (31-60 days past due) |
Severe | Severe delinquency (61-90 days past due) |
ChargeOff | Loan charged off |
Collection Status Flow:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π Collection Status Flow]
direction LR
A[β
Current] --> B[β οΈ Early<br/>1-30 DPD]
B --> C[β οΈ Late<br/>31-60 DPD]
C --> D[π¨ Severe<br/>61-90 DPD]
D --> E[π ChargeOff]
end
style A fill:#059669,stroke:#047857,color:#fff
style B fill:#d97706,stroke:#b45309,color:#fff
style C fill:#d97706,stroke:#b45309,color:#fff
style D fill:#dc2626,stroke:#b91c1c,color:#fff
style E fill:#dc2626,stroke:#b91c1c,color:#fff
Recasting Option Values
Recasting option values specify how loan schedules are recalculated after extra principal payments.
| Value | Description |
|---|---|
ReducePayment | Lower monthly payment, same term |
KeepPaymentSame | Same payment, shorter term |
Recasting Options:
%%{init: {'theme': 'base', 'themeVariables': {'background': '#ffffff', 'mainBkg': '#ffffff', 'clusterBkg': '#ffffff', 'clusterBorder': '#2563eb', 'primaryColor': '#2563eb', 'primaryTextColor': '#ffffff', 'titleColor': '#000000', 'lineColor': '#374151'}, 'flowchart': {'padding': 15, 'nodeSpacing': 25, 'rankSpacing': 30}}}%%
flowchart LR
subgraph MainContainer[π Recasting Options]
direction LR
A{π Recast} --> B[π° ReducePayment<br/>Lower Payment]
A --> C[π
KeepPaymentSame<br/>Shorter Term]
end
style A fill:#6b7280,stroke:#4b5563,color:#fff
style B fill:#2563eb,stroke:#1e40af,color:#fff
style C fill:#2563eb,stroke:#1e40af,color:#fff
Code Examples
Using Enums in Requests
The following examples demonstrate how to use enumerated values in API requests:
curl -X POST "https://api.demo.lms.lendfoundry.com/v1/payment-processor/payments" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"loanNumber": "LN-2024-001",
"paymentAmount": 500.00,
"paymentInstrument": "ACH",
"paymentType": "Schedule",
"recastingOption": "KeepPaymentSame"
}'// Example: Payment with enum values
const payment = {
loanNumber: 'LN-2024-001',
paymentAmount: 500.00,
paymentInstrument: 'ACH', // PaymentInstrumentValues
paymentType: 'Schedule', // PaymentTypeValues
recastingOption: 'KeepPaymentSame' // RecastingOptionValues
};
const response = await fetch(
'https://api.demo.lms.lendfoundry.com/v1/payment-processor/payments',
{
method: 'POST',
headers: {
'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
'Content-Type': 'application/json'
},
body: JSON.stringify(payment)
}
);
const result = await response.json();
console.log(result);# Example: Using enums with validation
from enum import Enum
class PaymentInstrument(Enum):
CASH = "Cash"
CHECK = "Check"
ACH = "ACH"
DEBIT_CARD = "DebitCard"
WIRE = "Wire"
class PaymentType(Enum):
SYSTEM = "System"
SCHEDULE = "Schedule"
PRINCIPAL_ONLY = "PrincipalOnly"
PAYOFF = "Payoff"
CUSTOM = "Custom"
class RecastingOption(Enum):
REDUCE_PAYMENT = "ReducePayment"
KEEP_PAYMENT_SAME = "KeepPaymentSame"
def make_payment(loan_number, amount, instrument: PaymentInstrument, payment_type: PaymentType, recasting: RecastingOption):
payload = {
"loanNumber": loan_number,
"paymentAmount": amount,
"paymentInstrument": instrument.value,
"paymentType": payment_type.value,
"recastingOption": recasting.value
}
import requests
url = "https://api.demo.lms.lendfoundry.com/v1/payment-processor/payments"
headers = {
"Authorization": "Bearer YOUR_ACCESS_TOKEN",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
response.raise_for_status()
return response.json()
# Usage
result = make_payment(
"LN-2024-001",
500.00,
PaymentInstrument.ACH,
PaymentType.SCHEDULE,
RecastingOption.KEEP_PAYMENT_SAME
)import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
import java.net.URI;
public class PaymentExample {
public static void makePayment() throws Exception {
String requestBody = """
{
"loanNumber": "LN-2024-001",
"paymentAmount": 500.00,
"paymentInstrument": "ACH",
"paymentType": "Schedule",
"recastingOption": "KeepPaymentSame"
}
""";
HttpClient client = HttpClient.newHttpClient();
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://api.demo.lms.lendfoundry.com/v1/payment-processor/payments"))
.header("Authorization", "Bearer YOUR_ACCESS_TOKEN")
.header("Content-Type", "application/json")
.POST(HttpRequest.BodyPublishers.ofString(requestBody))
.build();
HttpResponse<String> response = client.send(request,
HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
}
}Best Practices
Enum Usage Guidelines
-
Use exact values: Enum values are case-sensitive. Use the exact string as shown in the tables above.
-
Validate before sending: Validate enum values in your application before making API requests to avoid errors.
-
Handle invalid values: API responses will return validation errors if invalid enum values are used. Handle these errors gracefully.
-
Use constants: In your code, define constants or enums for these values to avoid typos and ensure consistency.
-
Check API responses: API responses may include enum values. Use these to understand the current state of resources.
Common Errors
| Error | Cause | Solution |
|---|---|---|
Invalid enum value | Wrong case or typo | Use exact value from table |
Value not allowed | Value not in enum list | Check enum definition |
Missing required field | Enum field not provided | Include required enum field |
Related Documentation
Updated 3 months ago
