Skip to content

Read all tickets of a site

Tickets — punch list items — are the work tracked on a site: something to fix, someone to fix it, a status that moves. Unlike detections they belong to the site, not to one flight.

Terminal window
curl -X GET "https://api.sitemark.com/layerFeatures?site_id=<site-id>&semantic_type=PUNCH_LIST_ITEMS&_pageSize=1000" \
-H "Authorization: ApiKey <your-api-key>"

That is every ticket on the site. Paginate with _page until you reach pagination.pageCount — see Pagination.

Filtering tickets by operation_id returns nothing. They are site-level and persist across flights; scoping them to a single capture matches no records. Same for components and annotations — see Data model.

This is the part that trips people up. Most properties are keyed by property-definition UUID, but ticket status and assignee are built-in properties: they come under their own names, STATUS and ASSIGNEE, and they are not in the property definitions list.

{
"id": 481920,
"visible_id": null,
"properties": {
"VISIBLE_ID": { "defaultValue": 142 },
"STATUS": { "value": "IN_PROGRESS" },
"ASSIGNEE": { "value": 3312 },
"3f2a1c84-...": { "value": "custom property — resolve this one" }
}
}

Each property is an object: read its value, or its defaultValue when value is missing or null. The ticket number is in properties.VISIBLE_ID.defaultValue; visible_id is null for tickets. STATUS is one of TO_DO, PLANNED, IN_PROGRESS, RESOLVED, WONT_DO or CLOSED, and ASSIGNEE is a person or a user group. Its value has two shapes: a v1 user or group id (a number, not a principal id, as above) or a v2 value { "version": "2", "principal_id": <id> }. Read both: older values stay v1. Resolve both to a name with List principals, as described in Resolve ASSIGNEE and USER values.

You can also sort on them directly — _sortBy=properties.STATUS — and built-in keys sort correctly whether or not the request is scoped to one dataset. See List layer features.

So when you build your UUID → name map from List property definitions, leave any key that is not a UUID exactly as it is rather than treating the lookup miss as an error. See How properties are keyed.

Instead of re-fetching everything, ask for the tickets of each ticket form that changed since a time, with dataset_id and updated_at[gte]. A site can have more than one ticket form; find them with List datasets (site_id=<site-id>&semantic_type=PUNCH_LIST_ITEMS). For each form:

Terminal window
curl -g -X GET "https://api.sitemark.com/layerFeatures?dataset_id=<dataset-id>&updated_at[gte]=2026-11-02T05:55:00Z&_sortBy=%2Bupdated_at&_sortBy=%2Bid&_pageSize=10000" \
-H "Authorization: ApiKey <your-api-key>"

See Sync tickets with your work system for the full polling recipe.

Annotations read the same way — swap the semantic_type. They are created per flight, so filter by operation_id for one flight, or by site_id for every flight at once. See Semantic types for the values.