Look up mortgage-rate context for a US postal code

View all Realty in US Property & Mortgage Data endpoints →

Request mortgage-rate information for the required postal_code query string, using a US ZIP code such as 90004. Keep the ZIP code as a string to preserve any leading zero. No recorded request to this operation is included in the evidence, so live availability, ZIP coverage, freshness, and returned rate units are unverified. The available documentation example is incomplete and shows top-level disclosures, meta, primary, providers, and rates. The disclosures object contains advertising_disclosure and rate_disclosure, while meta contains count and version. The providers array includes Name, Logo, Url, DisclaimerFull, and DisclaimerShort fields. Documented rates records include advertiser, rate, aprVal, loanTypeDisplayName, loanPayment, loanFees, points, isSponsored, and cpcUrl. These are source-example field names, not confirmed current response guarantees; the example does not establish observation timestamps or the interpretation and units of every amount. Display interest rate and APR separately, retain applicable disclosures and sponsorship labels, and verify loan assumptions before comparing payments or fees. Do not pass a returned rate directly into a mortgage calculator without confirming its numeric convention. This ZIP-based lookup is rate context, not a personalized offer, lender commitment, loan approval, or guaranteed real-time quote.

API Features

Single-ZIP mortgage context request Use the required postal_code string to scope a rate-information request without substituting a city name, address, or property identifier.
Separate rate and APR example fields The unverified documentation example distinguishes rate from aprVal. Keep these labels separate and verify units before rendering numeric comparisons.
Loan cost and product descriptors Documented rate entries contain loanTypeDisplayName, loanPayment, loanFees, and points; validate loan assumptions and units before interpreting these as comparable offers.
Disclosure and sponsorship metadata The source example includes advertising_disclosure, rate_disclosure, disclaimer fields, and isSponsored for transparently labeled rate-context displays.
Explicit freshness and coverage limits No request was recorded for this endpoint. ZIP coverage, current response structure, rate observation times, and live-quote status remain unverified.

Live API Demo

GET /api/project/realty-in-us/mortgage-v2-check-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/mortgage-v2-check-rates?key=<API_KEY>&postal_code=90004'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What input is required for the mortgage-rate lookup?

Supply postal_code as a US ZIP-code string, for example 90004. It is the only documented input for this operation; keep it as a string so a leading zero is not lost.

Have the returned rate records been verified with a recorded request?

No request was recorded for this endpoint. The available source example is incomplete and documents disclosures, meta, primary, providers, and rates, but does not confirm the current schema, ZIP coverage, or freshness.

What is the difference between rate and aprVal?

The source example has separate rate and aprVal fields for interest-rate and APR information. Do not collapse them into one label or assume their numeric convention is confirmed; verify units and loan assumptions before comparing records.

Can I treat a listed payment or rate as my approved lender offer?

No. A postal-code lookup does not establish borrower eligibility, personalized pricing, approval, or a lender commitment. Documented loanPayment, loanFees, points, and loanTypeDisplayName fields need context and are not verified personalized terms.

Can I copy a returned rate directly into a payment calculation?

Not without checking its units. The payment-calculation operation was verified using fractional annual rates, but the rate lookup has no recorded request confirming its output convention. Confirm the convention and let the user deliberately choose the assumption.

How should advertising and rate disclosures be handled?

Retain applicable advertising_disclosure and rate_disclosure text, documented disclaimer fields, and any isSponsored indicators alongside displayed records. Their presence in the source example is not proof that every current response will contain all of them.

Related operations

Guides

View Subscription Plans →