Current Challenges:

The Historical Records API returns the complete history with no way to retrieve only recent changes.

There is no filter for:

history_change_type

history_created_at

The Records API updated_at timestamp does not reflect delete events.

Incremental synchronization requires downloading and processing the entire history dataset repeatedly.

The solution does not scale well for large production environments.

We would appreciate one or more of the following enhancements:

Option 1 (Preferred)

Add filtering support to the Historical Records API, for example:

history_created_at >= <datetime>

history_change_type = deleted

Other date range filters for incremental synchronization

This would allow clients to retrieve only the records that changed during a specified time period.

Option 2

Update the updated_at field in the Records API whenever a record is deleted.

This would enable integrations to detect delete events using the existing incremental synchronization logic without requiring a full history scan.