Confirmation
Verification steps that run after the main Facility / Supplier Ingestion workflow completes. These requests confirm that ingested data has been persisted correctly and is available through the standard query endpoints.
These steps are kept separate from the core sequence because they read
through the standard query endpoints (/locations/*, /metrics/*)
rather than the ingestion task itself โ the same endpoints the rest of
the platform uses. That is what makes them a genuine confirmation: if the
data shows up here, scoped by filter[assets.task_id], it has been
persisted and is queryable, not just staged inside the task.
โถUse cases
- Post-ingestion validation โ verify that uploaded assets appear as expected in the locations and metrics endpoints
- Automated smoke tests โ run confirmation requests in CI/CD pipelines after an ingestion job finishes
- Data reconciliation โ compare ingestion results against location and metric queries to ensure consistency
โถStep overview
- Query facilities via
GET /locations/facilitiesand confirm the expected records exist - Query plots via
GET /locations/plotsand verify plot geometries and metadata - Retrieve deforestation and emissions metrics to confirm processing completed successfully
โถPrerequisites
- A completed Facility / Supplier Ingestion workflow (all prior steps must have finished successfully)
- Valid API key in the
x-api-keyheader