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
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-v2-check-rates 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'
Query Result
Use Cases
- Prototype a ZIP-keyed local mortgage-rate panel, enabling production display only after checking the response shape and coverage for the selected postal code.
- Design a rate-table view that labels interest rate, APR, loan type, fees, and points separately instead of ranking entries by a single ambiguous number.
- Build a disclosure area that retains advertising and rate caveats alongside any documented sponsorship indicators in returned records.
- Create an explicit user-selected rate-to-calculator handoff only after confirming rate units and the associated loan assumptions, rather than treating a listed rate as approval.
- Add an unknown-freshness state for postal-code rate results when no trustworthy observation date is present, avoiding a misleading live-rate badge.
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.