Retrieve location-based mortgage rate reference data

View all Realty in US Property & Mortgage Data endpoints →

Request finance-rate reference information using the required loc postal-code string. The documented example is loc=93505; no other input, lender selector, loan amount, or borrower profile is exposed by this operation. No successful probe is supplied, so the response fields described here come only from an unverified source example. That example has top-level meta and rates objects. The rates object contains string-valued average_rate_10_year, average_rate_15_year, average_rate_20_year, and average_rate_30_year reference fields; average_rate_30_year_fha and average_rate_30_year_va fields; and average_rate_51_arm and average_rate_71_arm fields labeled for adjustable-rate categories. It also contains numeric insurance_rate and property_tax fields and a nested meta.warnings string. The supplied example does not establish a quotation date, refresh interval, lender attribution, APR, discount points, eligibility requirements, or complete unit and calculation rules. Treat these fields as indicative context, not an available loan offer or a guaranteed current rate. Numeric-looking average-rate values are strings in the source example; validate their format and meaning before displaying or calculating with them. Do not infer tax or insurance amounts from the numeric fields without verified units. This operation retrieves reference data; it does not calculate monthly payments. Keep retrieved values separate from any explicitly selected assumptions used in a mortgage calculator.

API Features

Postal-code finance context Retrieve location-oriented rate reference data with the single required loc postal-code string. The documented example is 93505.
Term-labeled average-rate fields The unverified source example lists separate average_rate_10_year, average_rate_15_year, average_rate_20_year, and average_rate_30_year values as strings.
FHA, VA, and ARM reference slots The example distinguishes 30-year FHA and VA fields from 51_arm and 71_arm fields. Their presence does not verify product availability, eligibility, or quoted terms.
Separate tax and insurance signals The example includes numeric property_tax and insurance_rate fields alongside rate references. Their units and conversion into payment amounts are not established.
Warning-aware rate presentation The example includes rates.meta.warnings. Preserve relevant warning context when present and do not imply that a successful retrieval verifies rate freshness.

Live API Demo

GET /api/project/realty-in-us/finance-rates

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/finance-rates?key=<API_KEY>&loc=<loc>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does loc accept?

loc is a required postal-code string. The documented example is 93505. Keep it as a string so a leading zero is not lost; no city-name or coordinate input is documented for this operation.

Which rate fields are documented in the example?

The unverified source example contains average_rate_10_year, average_rate_15_year, average_rate_20_year, average_rate_30_year, average_rate_30_year_fha, average_rate_30_year_va, average_rate_51_arm, and average_rate_71_arm under rates. These are source-example fields, not fields confirmed by a successful probe.

Are these current lender quotes or guaranteed offers?

No such guarantee is established. The supplied evidence has no successful probe, verified update frequency, quotation date, lender attribution, APR, points, or borrower-eligibility rules. Use the results as reference context rather than an available lending offer.

Are rate, tax, and insurance values returned in the same type?

Not in the source example. The average_rate fields are strings, while insurance_rate and property_tax are numeric. Their complete units and calculation conventions are not documented here, so validate them rather than automatically treating each number as a percentage or currency amount.

Does this endpoint calculate my monthly mortgage payment?

No. It exposes only the loc input and returns reference-rate information in the source example, not a payment calculation. Keep any chosen mortgage-calculator rate separate from the retrieved reference and do not apply it silently.

Where are response warnings represented?

The unverified example includes a string at rates.meta.warnings as well as a top-level meta object. A verified warning structure and observation time are not established; inspect an actual response and display meaningful warnings when present.

Related operations

Guides

View Subscription Plans →