/trulia/properties

POST /api/trulia/properties

Price: 10 credits

Get full Trulia property details by numeric ID (or property URL): address, location and coordinates, listing status, price (listing price or Trulia Estimate), bedrooms, bathrooms, floor space, property type, description, photos, MLS number, listing agent and broker, list date, full home details (interior, property, community, lot), price history, tax and assessment, and local market trends.

How to use it

Fetch a single Trulia property by numeric ID (e.g. 119623659) or a property URL (https://www.trulia.com/home/...-{id}). Returns one item with address, city/state/zip, neighborhood, latitude/longitude, status, price/formatted_price/price_type, bedroom_count, bathroom_count, floor_space_sqft, property_type, description, image and images, mls_number, listing_agent, listing_broker, listed_at, home_details, price_history, tax_assessment and market_trends.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Trulia property numeric ID or a property URL containing it (examples: "119623659", "https://www.trulia.com/home/2001-faro-dr-4-austin-tx-78741-119623659"; minLength: 1)

Response

• @type string (default: "TruliaProperty")
• id string required
• url string required
• address string nullable
• street_address string nullable
• city string nullable
• state string nullable
• zip_code string nullable
• neighborhood string nullable
• latitude number nullable
• longitude number nullable
• status string nullable
• is_active_for_sale boolean nullable
• is_active_for_rent boolean nullable
• is_off_market boolean nullable
• is_foreclosure boolean nullable
• property_type string nullable
• price number nullable
• formatted_price string nullable
• price_type string nullable
• bedroom_count number nullable
• bathroom_count number nullable
• floor_space_sqft number nullable
• lot_size string nullable
• description string nullable
• image string nullable
• images array (default: [])
• photo_count integer nullable
• mls_number string nullable
• listing_agent string nullable
• listing_broker string nullable
• listed_at string nullable
• home_details array (default: [])
  • @type string (default: "TruliaPropertyFeatureCategory")
  • name string required
  • attributes object (default: {})
    • * string
• price_history array (default: [])
  • @type string (default: "TruliaPropertyPriceHistoryEvent")
  • date string nullable
  • event string nullable
  • price number nullable
  • formatted_price string nullable
  • source string nullable
• tax_assessment object nullable
  • @type string (default: "TruliaPropertyTaxAssessment")
  • year integer nullable
  • tax_value number nullable
  • total_assessment number nullable
• market_trends object nullable
  • @type string (default: "TruliaPropertyMarketTrends")
  • market_condition string nullable
  • avg_sale_price number nullable
  • sale_to_list_price string nullable
  • price_per_sqft string nullable
  • available_listings string nullable
  • last_updated string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Property not found (well-formed but nonexistent ID, or page has no property) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.