3 Get Validated Assets
โถStep 3: Get Validated Assets
Retrieve the validated entity results as a table. Use include=normalised_data,assessments
to get full entity data with coordinates, commodity type, and assessment values
(core confidence, EUDR add-ons, etc.).
โถWhat this step does
It returns the actual entity rows for the staged task โ one per uploaded
location โ with the normalised_data Epoch resolved (canonical name,
country, coordinates, commodity) and the assessments slots it computed
during staging (core confidence, and any EUDR / hazard / infrastructure
add-ons). This is the full, inspectable picture of what the upload
became, before any metrics run.
โถWhy it's needed
This is the review gate that makes the facility/supplier workflow distinct from Quick Ingestion. Metric processing is the expensive part of the pipeline, so before you commit to it you want to see how Epoch interpreted each row: did it match the right place, at what confidence, with commodity presence and road access confirmed? Reading the validated assets here lets you catch bad matches and decide which entities are worth processing โ the filters you apply in this step become the scope you pass to Step 4.
โถWhy include normalised_data and assessments
Without include=normalised_data,assessments you get the bare asset
envelope and would have to trust the raw upload as-is. Pulling both
relationships in surfaces the resolved fields and the confidence scoring
in one call, which is exactly the data the review table and the
confidence filters (filter[assessments.core.confidence_level]) key off.
โถRequest
GET /ingestions/assets/:id?include=normalised_data,assessments
Query parameters:
| Parameter | Description |
|---|---|
include | Comma-separated: assessments, normalised_data |
page[number] | Page number (default: 1) |
page[size] | Items per page (default: 25, max: 100) |
filter[assessments.core.confidence_level] | eq:high, eq:medium, eq:low |
filter[assessments.core.confidence_score] | gte:0.8, lt:0.5, etc. |
filter[normalised_data.commodity_type] | Filter by commodity type |
filter[normalised_data.location_type] | eq:facility or eq:plot |
filter[tags] | Filter by tag name (e.g., batch-q1) |
โถValidation Results Table
Each row's relationships.assessments.attributes carries one slot per
group (core, art9, art10, hazard, infrastructure, eudr).
Slots the requesting org cannot see (or that haven't been run yet)
are null. The columns below pull from the core slot and from
normalised_data:
| Column | Source | Description |
|---|---|---|
| Name | asset_data.supplier_name or normalised_data.normalized_name | Entity name |
| Location | normalised_data.normalized_country + lat/lng | Country code and coordinates |
| Commodity | normalised_data.commodity_type | Commodity type |
| Confidence | assessments.core.confidence_level | Color-coded badge (green/yellow/red) |
| Score | assessments.core.confidence_score | Numeric confidence (0โ1) |
| Producer | assessments.core.producer_confirmed | Whether producer presence was confirmed |
| Commodity Presence | assessments.core.flags.commodity_presence | Whether commodity detected within 5km |
| Road Access | assessments.core.flags.road_access | Whether location has road access |
| Status | attributes.status | Entity processing status |
โถFrontend Usage
- Sortable table: Render entities as rows with the columns above
- Confidence badges: Color-code by level (green = high, yellow = medium, red = low)
- Filtering: Filter by confidence level to focus on high-confidence results
- Tag filter: Use
filter[tags]=batch-q1to scope to specific upload batches - Pagination: Navigate through results using
page[number]andpage[size]
โถNext Step
โ Step 4: Process Metrics (PUT /ingestions/assets)