Changelog
Start typing to search…
Back to All
added

[January 27, 2025] Property Data Updates & Incremental Sync Support

2 months ago by ReadMe API

v0.26.0

This release introduces new capabilities for tracking data freshness and enabling efficient incremental updates across our property endpoints.

What's New & Why It Matters:

  • 🔍 Track New Properties: Find properties newly added to our database since your last query using Property Search endpoint's new record_added_date filtering
  • 🔄 Efficient Data Sync: Only pull new or updated records using Property Events endpoint's new record_updated_date filtering

Added

Property Search Endpoint

New Query Parameters

  • record_added_date_start: Specifies the beginning of the query period for when properties were added to the property record tracking system, inclusive, in ISO 8601 format (YYYY-MM-DD). Properties existing before tracking implementation are marked as 2024-12-13. Defaults to 2024-12-13.
  • record_added_date_end: Specifies the end of the query period for when properties were added to the property record tracking system, inclusive, in ISO 8601 format (YYYY-MM-DD). Properties existing before tracking implementation are marked as 2024-12-13. Defaults to NULL.

New Response Field

  • record_added_date: Date when property (parcl_property_id) was added to the property record tracking system. Properties that existed before tracking implementation are marked as 2024-12-13. Properties added after this date (such as new construction) will show their actual date of addition to the index.

Example Response

{
  "items": [
    {
      "parcl_property_id": 0,
      "address": "string",
      "unit": "string",
      "city": "string",
      "zip_code": "string",
      "state_abbreviation": "string",
      "county": "string",
      "cbsa": "string",
      "latitude": 0,
      "longitude": 0,
      "property_type": "string",
      "bedrooms": 0,
      "bathrooms": 0,
      "square_footage": 0,
      "year_built": 0,
      "cbsa_parcl_id": 0,
      "county_parcl_id": 0,
      "city_parcl_id": 0,
      "zip_parcl_id": 0,
      "event_count": 0,
      "event_history_sale_flag": 0,
      "event_history_rental_flag": 0,
      "event_history_listing_flag": 0,
      "current_new_construction_flag": 0,
      "current_owner_occupied_flag": 0,
      "current_investor_owned_flag": 0,
      "current_entity_owner_name": "string",
      "record_added_date": "2025-01-24"
    }
  ],
  "account": {
    "est_credits_used": 250,
    "est_remaining_credits": 9750
  }
}

Property Events Endpoint

New Query Parameters

  • record_updated_date_start: Specifies the beginning of the query period for when property event metadata was last modified in the property record tracking system, inclusive, in ISO 8601 format (YYYY-MM-DD). Events existing before tracking implementation are marked as 2024-12-13. Defaults to 2024-12-13.
  • record_updated_date_end: Specifies the end of the query period for when property event metadata was last modified in the property record tracking system, inclusive, in ISO 8601 format (YYYY-MM-DD). Events existing before tracking implementation are marked as 2024-12-13. Defaults to NULL.

New Response Field

  • record_updated_date: Date when property (parcl_property_id) event metadata was last modified in the property record tracking system. Events that existed before tracking implementation are marked as 2024-12-13. Events modified after this date (such as sale index updates or ownership changes) will show their actual date of modification in the index.

Example Response

{
  "items": [
    {
      "parcl_property_id": 0,
      "event_date": "2025-01-24",
      "event_type": "string",
      "event_name": "string",
      "price": 0,
      "owner_occupied_flag": 0,
      "new_construction_flag": 0,
      "investor_flag": 0,
      "entity_owner_name": "string",
      "current_owner_flag": 0,
      "transfer_index": 0,
      "true_sale_index": 0,
      "record_updated_date": "2025-01-24"
    }
  ],
  "account": {
    "est_credits_used": 250,
    "est_remaining_credits": 9750
  }
}

Example Use Cases

Tracking New Properties Added to Database

To identify any new properties added to the database (could include new construction, newly discovered properties, or data improvements):

# Get all properties added in the last week
new_properties = client.property.search.retrieve(
    record_added_date_start='2025-01-17',
    record_added_date_end='2025-01-24'
)

print(f"Found {len(new_properties)} new properties added to the database")

Monitoring Recent Events

To track properties with new or updated sale events:

# Get all sale events that were recorded or updated in the last week
recent_sales = client.property.events.retrieve(
    parcl_property_ids=[...],
    event_type='SALE',
    record_updated_date_start='2025-01-17',
    record_updated_date_end='2025-01-24'
)

# These could include:
# - Newly recorded sales
# - Updated sale events (e.g., transfer index changes)
# - Backfilled historical sales
print(f"Found {len(recent_sales)} new or updated sale events")

Note: Property record tracking began on December 13, 2024. All properties and events that existed in our database before this date are marked with "2024-12-13" as their record_added_date or record_updated_date. This provides a clear demarcation between historical data and new/modified records.