Estimate Financing by Cash Down Payment
View All Realtor Property Data APIs →Supply homePrice and downPaymentPrice with mortgageLoanType, interestRate, propertyTaxRate and homeInsurance. The documented downPaymentPrice input is a cash contribution rather than a percentage; source examples are scenario inputs, not API pricing. This route was not live-tested, so payment fields, loan-term interpretation, rate scale and insurance period are unconfirmed. Compare scenarios only after verifying all units and returned calculations, and describe the result as an estimate rather than a lender quote or personalized recommendation.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/realtor/property-calculate-down-payment-price API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realtor/property-calculate-down-payment-price?key=<API_KEY>&homePrice=5450000&downPaymentPrice=1090000&interestRate=0.06577&propertyTaxRate=0.00865&mortgageLoanType=30&homeInsurance=1892'
Query Result
Use Cases
- Evaluate several candidate home prices for a buyer with a fixed cash contribution.
- Test how an additional cash down payment changes a validated estimate with other inputs unchanged.
- Compare fixed-amount and percentage contribution routes only after normalizing their accepted units.
- Review estimate behavior near a selected contribution threshold without presenting personalized loan advice.
Frequently asked questions
Is downPaymentPrice a percentage?
No. The documented input represents a cash amount and is separate from downPaymentPercentage. Verify the amount unit and actual calculation behavior before adoption.
Can I compare home prices while keeping the down payment fixed?
That is a suitable evaluation scenario: hold downPaymentPrice and other assumptions constant while changing homePrice. This operation was not live-tested, so validate units and output first.
Can I directly compare this result with the percentage-based calculation?
First normalize down-payment, interest, tax and insurance units, then construct equivalent scenarios. Similar field names alone do not prove equivalent calculations.