Get Ingestion Asset
Get the processing results for a specific ingestion asset.
โถUse Cases
- Check which entities (facilities, plots) were created or matched from an upload.
- Debug why certain rows in an upload were rejected.
โถFilters
Use filter[field]=condition:value to narrow results. See Query Parameters for full syntax.
filter[tags]=eq:verifiedโ filter by tag namefilter[assets.data.ADMIN1_NAME]=eq:Bantenโ filter by source data fields using dot-notationfilter[assets.data.ASSET_NAME]=contains:Aberdeenโ substring match on source datafilter[compliance]=eq:non_compliantโ filter by per-location EUDR deforestation status (non_compliant/pending/compliant/excluded/not_assessed); see Deforestation roll-up below
โถThis upload's records, and their history
Every row here is one record โ this task's view of a location โ so every row
carries attributes.row_id and a links.history pointing at
Get Record History.
That matters most on an older task. A row here can be a record that a later
upload has already replaced, and this endpoint still returns it, because a task
is the historical record of what it ingested. links.history is how you find
out: it returns the location's whole record set with is_live on each, so you
can see whether the row you are reading is still current.
This endpoint is also where a plot location's handle comes from.
GET /ingestions/assets/latest folds a plot task into one row, and a folded row
is not one record, so it carries no row_id.
โถPredecessors and metrics
?include=superseded and ?include=metrics[.<category>] are accepted here as
on the list endpoints. Every row of this response is one record, so both apply
to every row.
?include=superseded is useful on an OLDER task, where a row may already have
been replaced: it shows what THIS record replaced, while links.history shows
the location's whole set with is_live on each.
Ask for one metric category rather than all four unless you need them โ one statement runs per category per location type. See List All Ingestion Assets for the full reference.
โถDDS records (include=audit_trails)
include=audit_trails)Accepted here as on the list endpoints: every EUDR audit trail covering each
row's location, with its lifecycle_status, its TRACES reference_number, and
pinned_record_is_live โ whether the record the filing was pinned from is
still the current one for that location.
Scoping the read to one task does NOT scope the record set to that task. The
set is resolved across each row's supersession lineage, so a filing pinned from
an upload that a later one replaced is still reported, with
pinned_record_is_live: false.
Opt-in and strictly more expensive than the scalar audit_trail_id. See
List All Ingestion Assets for the full
reference.
โถDeforestation roll-up (include=deforestation)
include=deforestation)Add include=deforestation (or ?deforestation=<view>) to attach a per-location EUDR deforestation roll-up under attributes.deforestation on each item โ the compliance summary for that item's location_id (total_plots, compliant_plots, non_compliant_plots, unknown_plots, total_area_ha, compliant_area_ha):
GET /ingestions/assets/:id?include=deforestation
A facility/shed aggregates its whole catchment; a plot location rolls up the parts of its latest upload. Facility/shed roll-ups are cached at task completion (no live catchment scan); plot verdicts are computed live.
Pick the variant with ?deforestation= (also enables the block): ccdc (CCDC metrics), eudr (EUDR window), or true/user/omit for the org default (prioritised fallback โ prefer a variant with an assessed metric, then CCDC, then EUDR window).
Filter to a status with filter[compliance]=eq:non_compliant|pending|compliant|excluded|not_assessed (per location, against the selected variant; meta.total reflects it). See Query Parameters โ EUDR compliance verdict.
โถGeometry (include_geometries)
include_geometries)Geometry lives inside the normalised_data relationship and is opt-in. To
get it on the JSON response you need both include=normalised_data and
include_geometries=true:
GET /ingestions/assets/:id?include=normalised_data&include_geometries=true
Without the flag, normalised_data is returned without its geometry.
Passing include_geometries=true without include=normalised_data is a no-op.
A GeoJSON Accept format (application/geo+json) always includes geometry.
See Query Parameters โ Geometry.
Required scope:
ingestions:read