Lot Size Filtering with API Parameters

Overview

Our API supports lot size filtering through the minLotSizeSqft and maxLotSizeSqft parameters. These parameters allow you to find listings that meet specific lot size requirements by specifying minimum and maximum lot sizes in square feet.

Key Points

• API Parameters: Use minLotSizeSqft and maxLotSizeSqft for lot size filtering
• Unit Requirement: Both parameters accept values in square feet only
• Conversion Required: Regardless of how users provide lot size requirements (acres or square feet), convert to square feet before making API requests
• Backend Processing: Our system handles MLS® data transformation automatically, regardless of the original measurement unit

Acre to Square Feet Conversion

Conversion Formula

1 acre = 43,560 square feet
Square feet = Acres × 43,560

Common Conversions

API Request Examples

Example 1: Properties with at least 1 acre

GET /listings?minLotSizeSqft=43560

Example 2: Properties between 0.5 and 2 acres

GET /listings?minLotSizeSqft=21780&maxLotSizeSqft=87120

Example 3: Properties with maximum 0.25 acres

GET /listings?maxLotSizeSqft=10890

Example 4: Large properties (5+ acres)

GET /listings?minLotSizeSqft=217800

Example 5: Combined with other filters

GET /listings?minLotSizeSqft=43560&maxLotSizeSqft=130680&minPrice=500000&maxPrice=1000000

Code Examples

JavaScript Conversion Function

function acresToSquareFeet(acres) {
    return acres * 43560;
}

// Usage example
const minAcres = 1.0;
const maxAcres = 3.0;
const apiUrl = `https://api.repliers.io/listings?minLotSizeSqft=${acresToSquareFeet(minAcres)}&maxLotSizeSqft=${acresToSquareFeet(maxAcres)}`;

Python Conversion Function

def acres_to_square_feet(acres):
    return acres * 43560

# Usage example
min_acres = 1.0
max_acres = 3.0
api_url = f"https://api.repliers.io/listings?minLotSizeSqft={acres_to_square_feet(min_acres)}&maxLotSizeSqft={acres_to_square_feet(max_acres)}"

Best Practices

1. API Requirement: Always convert to square feet before making API requests, regardless of input unit
2. Unit Flexibility: Design your application to accept lot sizes in any unit that makes sense for your users
3. Precision: Round converted values appropriately (whole numbers are usually sufficient)
4. Validation: Ensure converted values are positive integers
5. Testing: Test edge cases like very small (< 0.1 acres) and very large (> 100 acres) lot sizes

Troubleshooting

Common Issues

• No Results: Check that your converted square footage values are reasonable
• Too Many Results: Verify that your minimum and maximum values aren't reversed
• Invalid Parameters: Ensure you're using minLotSizeSqft and maxLotSizeSqft (not minLotSize or similar)

Support

If you encounter issues with lot size filtering, please provide the following context to our support team:

• The original acre values from your user
• The converted square footage values
• The complete API request URL
• Any error messages received

Updated on: 16/07/2025