See what changed on a record
Every edit to a layer feature property is recorded in a log. That log is how you answer “who closed this ticket”, “when did this deviation get resolved”, or “what moved since yesterday” without diffing snapshots yourself.
The call
Section titled “The call”curl -X GET "https://api.sitemark.com/propertyChanges?layer_feature_id=<layer-feature-id>&_pageSize=100" \ -H "Authorization: ApiKey <your-api-key>"Use the integer id from the layer feature, not its visible_id. History is always read per
layer feature, up to 200 ids per call.
Reading the entries
Section titled “Reading the entries”Each entry names the property that changed, its new value (new_value), and who made the change.
There is no old value: compare with the previous change of the same property. The property_key is
either:
- a built-in key —
STATUS,ASSIGNEE,VOLUME— which is its own name and is not in the property definitions list, or - a property-definition UUID, which you resolve to a name via List property definitions.
Who made the change is in principal_id: a user, a user group or an API key. Resolve it to a type
and a name via List principals, up to 200 ids per call.
The author of an older change who has since left the company still gets a name. An older change
can have no principal_id: then read user_id. user_id is deprecated. It is not a principal id,
so you cannot filter on it: list the principals and find the USER item whose user.id is equal
to it. A change made by Sitemark itself, or caused by another change, has neither.
Narrowing to one property
Section titled “Narrowing to one property”To follow just the status of a ticket, filter by key:
curl -X GET "https://api.sitemark.com/propertyChanges?layer_feature_id=<layer-feature-id>&property_key=STATUS&_pageSize=100" \ -H "Authorization: ApiKey <your-api-key>"property_key only narrows within layer_feature_id — it cannot be used on its own, and takes at
most 200 keys.