2026-08-14
5 days ago
🚨 BREAKING CHANGES
Property Origin has been renamed to Data Lineage in the External API. This change affects only the optional lineage expansion available on retrieve operations. Data lineage remains excluded by default.
Changed operations
-
Retrieve a case (
GET /v1/cases/{id})- 🚨 [Removed] optional query parameter
property_origin - ✨ [Added] optional query parameter
data_lineage(boolean, default:false) - 🚨 When
data_lineage=true, renamedindividuals[].property_originstoindividuals[].data_lineage - 🚨 When
data_lineage=true, renamedcompanies[].property_originstocompanies[].data_lineage
- 🚨 [Removed] optional query parameter
-
Retrieve a company (
GET /v1/companies/{id})- 🚨 [Removed] optional query parameter
property_origin - ✨ [Added] optional query parameter
data_lineage(boolean, default:false) - 🚨 When
data_lineage=true, renamed response propertyproperty_originstodata_lineage
- 🚨 [Removed] optional query parameter
-
Retrieve an individual (
GET /v1/individuals/{id})- 🚨 [Removed] optional query parameter
property_origin - ✨ [Added] optional query parameter
data_lineage(boolean, default:false) - 🚨 When
data_lineage=true, renamed response propertyproperty_originstodata_lineage
- 🚨 [Removed] optional query parameter
Renamed component schemas
PropertyOrigin→DataLineagePropertyOriginValueSource→DataLineageValueSourcePropertyOriginValueSourceOrigin→DataLineageValueSourceOrigin
Migration notes
- Replace
property_origin=truewithdata_lineage=true. - Replace the
property_originsresponse key withdata_lineage. - Requests still using
property_originreturn200, but data lineage is omitted because the old parameter is ignored.