Skip to main content
Home
Products
Free Tools
Industries
Compare
Resources
Pricing
Enrich

Property Lookup API: address in, property record out

Turn a US address into the property record: beds, baths, square footage, year built, listing status, list price and last sale from public real-estate listing data. 15 credits, only charged on a match.

15 credits per lookupOnly charged on a matchSame credits as every other product
1Lookup property lookup API turning a US street address into a property record with beds, baths, square footage, year built, listing status and last sale

15

Credits per match

~$0.05-0.07 per property

0

Credits on a miss

no record, no charge

1-3 min

First live fetch

instant repeats for 7 days

Facts

No modeled value estimates

listing and sale record only

What Property Lookup gives you

The whole property record in one call

Beds, baths, square footage, home type and year built: the physical facts of the property, returned as one structured record from a single address string.

  • Beds, baths and square footage
  • Home type and year built
  • One address string in
  • Structured JSON out

Listing status and last sale together

See whether the property is on the market right now, with list price and days on market, next to the last sold date and price from the public record. Current asking and past paid, side by side.

  • For-sale or off-market status
  • List price and days on market
  • Last sold date and price
  • Photo count on the listing

Fetched live, cached for 7 days

Each first lookup is a live deep fetch of the property record, not a read from a database that went stale last year. It typically takes one to three minutes, and repeat lookups on the same address within 7 days return instantly from cache.

  • Live fetch, typically 1-3 min
  • Current listing status
  • Repeats instant for 7 days
  • No stale-database surprises

Only charged on a match

If the address does not resolve to a property record, you pay nothing. That makes it safe to run raw mailing lists and unverified addresses where a real share of the rows were always going to miss.

  • Zero credits on no match
  • Applies to bulk jobs too
  • Predictable cost on messy lists
  • No minimum commitment

About six cents per property

15 credits per matched property works out to roughly $0.07 on the Starter plan and $0.05 on Growth. Qualifying a 1,000-address mailing list costs about $53-75, and only the addresses that match bill at all.

  • 15 credits per match
  • ~$0.05 per property on Growth
  • ~$0.07 per property on Starter
  • Misses are free

The missing half of a skip trace

Skip Trace and Reverse Phone Lookup tell you who to call; Property Lookup tells you whether the address is worth the call: a 3-bed house that fits the buy box, an active listing, or a miss. Same credits, same API key, one workflow.

  • Pairs with Skip Trace
  • Pairs with Reverse Phone Lookup
  • One shared credit balance
  • Bulk CSV supported

Address in, listing facts out

01

Send a US address

POST one address string: street, city and state. No parcel number or other identifier needed; the lookup matches the string to the property record.

request

$ POST /v1/property-lookup

"address": "1417 Cedar Bend Dr,

Austin, TX 78758"

> one address string, that is it

02

We fetch the record live

First lookups run a live deep fetch of the property record, typically one to three minutes. Repeats on the same address within 7 days return instantly from cache.

processing

Address matched to property

Live record located

Listing and last sale read

Building record, 1-3 min fresh

03

Get the listing facts

Beds, baths, square footage, year built, listing status, list price and last sale land in one JSON payload. A match bills 15 credits; a miss bills nothing.

200 OK

address1417 Cedar Bend Dr

size3 bd, 2 ba, 1,642 sqft

last sold2016, $289,000

for_sale at $425,00015 credits on match

One endpoint. A US street address in, structured data out.

Same authentication, same credit balance, and the same response envelope as every other 1Lookup product. If you have already integrated one endpoint, this one is a URL change.

POST /v1/property-lookup
curl -X POST https://app.1lookup.io/api/v1/property-lookup \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "address": "1417 Cedar Bend Dr, Austin, TX 78758"
      }'
200 OK
{
  "classification": {
    "matched": true,
    "address": "1417 Cedar Bend Dr, Austin, TX 78758",
    "beds": 3,
    "baths": 2,
    "sqft": 1642,
    "home_type": "single_family",
    "year_built": 1998,
    "listing_status": "for_sale",
    "list_price": 425000
  },
  "insights": {
    "property_lookup_result": {
      "street_address": "1417 Cedar Bend Dr",
      "city": "Austin",
      "state": "TX",
      "zip_code": "78758",
      "days_on_market": 24,
      "last_sold_date": "2016-08-12",
      "last_sold_price": 289000,
      "photo_count": 31
    }
  },
  "metadata": { "credits_used": 15, "cache_hit": false }
}

What a matched property looks like

One call turns an address on a mailing list into a property you can qualify: the physical facts, the current listing and the last sale from the public record, side by side with the raw JSON your code receives.

api.1lookup.ioMatched: for sale
  • Address1417 Cedar Bend Dr, Austin, TX 78758
  • Home typeSingle family
  • Beds3 bd
  • Baths2 ba
  • Size1,642 sqft
  • Year built1998
  • Listing statusFor sale
  • List price$425,000
  • Days on market24
  • Last soldAug 2016 for $289,000
  • Photos on listing31
200 OK, 15 credits
{
  "classification": {
    "matched": true,
    "address": "1417 Cedar Bend Dr, Austin, TX 78758",
    "beds": 3,
    "baths": 2,
    "sqft": 1642,
    "home_type": "single_family",
    "year_built": 1998,
    "listing_status": "for_sale",
    "list_price": 425000
  },
  "insights": {
    "property_lookup_result": {
      "days_on_market": 24,
      "last_sold_date": "2016-08-12",
      "last_sold_price": 289000,
      "photo_count": 31
    }
  },
  "metadata": { "credits_used": 15 }
}

Every field you get back

No hidden tiers. Every field below is returned on a successful lookup at the price shown above.

Property

  • home_type
  • beds
  • baths
  • sqft
  • year_built

Listing

  • listing_status
  • list_price
  • days_on_market

Sale history

  • last_sold_date
  • last_sold_price

Identity & media

  • address
  • photo_count

Who uses Property Lookup

Real-estate investors qualifying seller leads

A motivated-seller lead is just an address until you know what stands on it. One call returns beds, baths, square footage and year built, so a lead that does not fit the buy box drops out before anyone drives to see it.

Skip tracers completing a trace

The phone side of a trace finds the person; this finds the property. Confirm the address in a file is a real residence, see whether it is currently listed for sale, and note the last sale on record, all from the address you already have.

Debt collection verifying assets

An address on file becomes asset context: the property type behind it, whether it is on the market, and what it last sold for from the public record, useful signal when prioritizing which accounts justify further work.

Wholesalers filtering direct-mail lists

Run the mailing list through before printing. Keep the single-family homes in the right size and age range, drop the condos and the addresses that do not resolve, and the misses cost nothing.

Frequently asked questions

What does Property Lookup return?

Give it a US street address and it returns the property record from public real-estate listing data: beds, baths, square footage, home type, year built, listing status, list price when the property is on the market, days on market, photo count, and the last sold date and price. One call turns an address on a list into a property you can actually evaluate.

What inputs do I need?

A single US address string with street, city and state is enough. The lookup matches it to the property record; you do not need a parcel number or any other identifier.

Am I charged when no property is found?

No. Property Lookup is success-billed: if the address does not resolve to a property record, zero credits are deducted. The 15-credit price applies only when a record comes back, and the same rule applies to API calls, the dashboard and bulk CSV jobs.

How long does a lookup take?

A first-time lookup runs a live deep fetch of the property record, so expect it to take on the order of a minute, typically one to three minutes and occasionally longer, rather than the sub-second responses of our phone and email products. Repeat lookups on the same address within 7 days are served from cache and return instantly.

What does it cost in dollars?

15 credits per matched property, about $0.07 on the Starter plan and $0.05 on Growth. No-match lookups cost nothing, so running a raw mailing list where some addresses never resolve only bills for the addresses that do.

Do you return an estimated home value?

No, and that is deliberate. We return facts from the listing and the public sale record: the list price when the property is on the market, and the last sold date and price. We do not return modeled value estimates. If you need a valuation, build it from the facts we hand you.

How does this fit a skip-trace workflow?

It is the property half of the trace. Skip Trace turns a name and address into phone numbers, and Reverse Phone Lookup turns a number into an identity; Property Lookup tells you what the address itself is: a 3-bed house last sold in 2016, an active listing, or nothing at all. Together they turn one lead into a contactable person at a qualified property.

Can I look up a whole list at once?

Yes. Upload a CSV with an address column and the bulk pipeline resolves every row. Rows where no property record is found cost nothing, so a half-clean or hand-built mailing list does not inflate the bill.

Start with Property Lookup today

7-day free trial. No contracts, cancel anytime, and your credits work across every product in the catalog.