Legacy mortgage payment calculation (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Retained for existing mortgage calculators using six required numeric query parameters: downpayment for the down payment, hoi for home insurance, price for the home price, rate for the interest rate, tax_rate for property tax and term for the mortgage loan type. Preserve these exact parameter names when auditing an older integration. The documented input example is downpayment=44980, hoi=56, price=224900, rate=3.827, tax_rate=1.2485549449920654 and term=30. These are example values, not documented defaults or a list of allowed choices. The supplied documentation example contains a meta object and a mortgage object. Example mortgage fields are down_payment, loan_amount, rate, term, principal_and_interest, monthly_property_taxes, monthly_home_insurance, monthly_mortgage_insurance, hoa_fees, monthly_payment and total_payment. The monthly_* field names distinguish monthly amounts, and principal_and_interest identifies a separate payment component. Do not equate monthly_payment, principal_and_interest and total_payment or infer which charges each aggregate includes without validation. No successful check of this deprecated calculation route is supplied; the response fields above are from an unverified documentation example. The brief parameter descriptions do not explicitly define currency, insurance input period, rate scale, tax-rate units or term units. A term example of 30 does not by itself establish an allowed-term list. Confirm those conventions and payment scope in the existing application before mapping inputs to a current calculator. This route is a legacy migration surface, not a recommended foundation for new calculators, an interest-rate feed, a lender quote or a loan approval decision.
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/realty-in-us/mortgage-calculate-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/mortgage-calculate-deprecated?key=<API_KEY>&downpayment=<downpayment>&hoi=<hoi>&price=<price>&rate=<rate>&tax_rate=<tax_rate>&term=<term>'
Query Result
Use Cases
- Audit a mortgage widget that already sends downpayment, hoi and tax_rate before changing its parameter mapping.
- Prepare migration fixtures from known loan scenarios and compare principal-and-interest, tax and insurance fields separately.
- Review whether an existing interface labels monthly_payment and total_payment as if they were interchangeable amounts.
- Record the legacy application's currency, insurance period, interest-rate scale, property-tax units and term convention before adopting a current calculator.
- Preserve a documentation-only mortgage response fixture for an older parser while clearly excluding it from verified lender estimates.
Frequently asked questions
Which parameters are required by this deprecated calculator?
All six documented query parameters are required numbers: downpayment, hoi, price, rate, tax_rate and term. Preserve their exact names in an existing integration; the published examples are not guaranteed defaults.
Is hoi monthly insurance, and is term measured in years?
Those input units are not explicitly defined in the supplied descriptions. The response example names a monthly_home_insurance field and the term example is 30, but neither establishes the full input convention. Confirm the units used by the existing calculator before migrating.
Which payment components appear in the documentation example?
The mortgage object includes principal_and_interest, monthly_property_taxes, monthly_home_insurance, monthly_mortgage_insurance, hoa_fees, monthly_payment and total_payment, along with down_payment, loan_amount, rate and term. This is an unverified example, not an observed response guarantee.
Can I treat monthly_payment as principal and interest only?
No. The example has separate principal_and_interest, monthly_payment and total_payment fields. Validate each amount's period and included charges before labeling it or comparing it with another calculator.
Is this endpoint suitable for a new lending quote experience?
No. It is deprecated and has no successful recorded check in the supplied evidence. Use it to audit a legacy integration, validate a current calculation route separately and do not present a calculation as a lender quote or loan approval.