Property Lookup
Beds, baths, square footage, year built and last sale for a US address.
curl -X POST https://api.1lookup.dev/v1/property-lookup \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"address":"1200 Example Ave, Austin, TX 78701"}'{
"success": true,
"data": {
"address": {
"line1": "1200 Example Ave",
"city": "Austin",
"state": "TX",
"zip": "78701"
},
"matched": true,
"property_type": "single_family",
"beds": 3,
"baths": 2,
"living_area_sqft": 1840,
"lot_size_sqft": 6534,
"year_built": 1978,
"last_sale": {
"date": "2019-06-14",
"price": 465000
},
"assessment": {
"assessed_value": 612400,
"tax_year": 2026
},
"owner_occupied": true
},
"meta": {
"credits_used": 15,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
addressstringrequiredUS street address. Example: 1200 Example Ave, Austin, TX 78701
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.property_typestringsingle_family, condo, townhouse or multi_family.
data.bedsnumberThe number of bedrooms on the property record.
data.bathsnumberThe number of bathrooms on the property record.
data.living_area_sqftnumberLiving area in square feet, returned alongside lot size.
data.year_builtnumberThe year the structure was built.
data.last_saleobjectThe date and price of the most recent recorded sale.
data.assessment.assessed_valuenumberThe value set by the taxing authority for the stated tax year.
data.owner_occupiedbooleanWhether the record indicates the owner lives at the property.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
15 credits. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases