Compare mortgage rates by financing scenario (deprecated)

View all Realty in US Property & Mortgage Data endpoints →

Legacy GET mortgage-rate comparison request for purchase or refinance scenarios. All query inputs are required: creditScore, loanPercent, loanPurpose, loanTypes, points, propertyPrice and zip. creditScore accepts the documented quality categories; loanPurpose selects purchase or refinance; loanTypes selects ALL or one documented fixed-rate or adjustable-rate code; and points selects all, zero, zero_to_one or one_to_two. The documented loanPercent example is 85.2, not the fractional representation 0.852; propertyPrice is a numeric price amount. No live response was observed for this deprecated route. The truncated, unverified documentation example contains disclosures.advertising_disclosure and disclosures.rate_disclosure, meta.count and meta.version, a primary boolean, a providers array, and a rates array. Visible rate-entry fields include advertiser, aprVal, rate, loanFees, loanPayment, loanTypeDisplayName, points and isSponsored. points is represented as a string in the example. The snippet does not establish complete field coverage, current rates, ranking rules or the precise units and periods of all financial values. Treat disclosures and sponsorship indicators as context, not proof that an entry is best for a borrower. Use this route only as a legacy migration reference. Do not silently replace its credit-category, purpose, loan-type, percentage and points filters with a postal-code-only rate lookup: that would lose unverified assumptions. Historical example values are not current lender quotes, rate locks, eligibility decisions or commitments to lend.

API Features

Purchase-or-refinance scenario choice Retain the explicit loanPurpose distinction between purchase and refinance when documenting an older mortgage comparison request.
Fixed and adjustable loan-type codes Preserve the documented ALL, fixed-term, FHA, VA and ARM selections without claiming that every product currently returns a rate.
Mortgage-points filtering contract Record the all, zero, zero_to_one and one_to_two request values separately from the string-valued points field shown in example rate entries.
Legacy comparison result mapping Identify rate, aprVal, loanFees, loanPayment and loanTypeDisplayName in the unverified sample while retaining disclosure and sponsorship context.

Live API Demo

GET /api/project/realty-in-us/mortgage-check-rates-deprecated

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/mortgage-check-rates-deprecated?key=<API_KEY>&creditScore=excellent&loanPercent=<loanPercent>&loanPurpose=purchase&loanTypes=ALL&points=all&propertyPrice=<propertyPrice>&zip=<zip>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Is this operation recommended for a new mortgage-rate comparison?

No. It is deprecated and no live response was observed. Its truncated documentation example is a migration reference, not evidence of current loan offers or a complete response contract.

Which loanPurpose and loanTypes values are documented?

loanPurpose accepts purchase or refinance. loanTypes accepts ALL, 30YrFixed, 30YrFixed_FHA, 30YrFixed_VA, 20YrFixed, 15YrFixed, 10YrFixed, 5Arm or 7Arm. These are documented request choices, not a guarantee that any particular product currently has results.

How should loanPercent and points be entered?

Keep the documented percentage-style loanPercent example 85.2 rather than changing it to 0.852. points accepts the strings all, zero, zero_to_one or one_to_two. The legacy notes do not further specify boundary behavior for the points ranges.

Which fields appear in the documented rate results?

The unverified example shows a rates array with advertiser, aprVal, rate, loanFees, loanPayment, loanTypeDisplayName, points and isSponsored. It also includes disclosures, meta.count, meta.version, primary and providers. The example is truncated, and points is a string there; do not infer complete field coverage or current pricing.

Can a ZIP-only rate lookup be used as a drop-in replacement?

Not without verifying the missing assumptions. This legacy request explicitly includes credit category, loan percentage, purchase or refinance purpose, loan type, points and property price. A ZIP-only lookup does not by itself establish equivalent filtering, results or financing terms.

Related operations

Guides

View Subscription Plans →