Skip to content
Darwin Evolution

Operational reports

Tracium exposes a set of aggregated reporting endpoints over your captured events. These are operational reports (alerts, documents, supplier performance, yields, inventory). They are not framework-formatted regulatory bundles.

Available endpoints

Section titled “Available endpoints”

All under /api/v1/reports/*, authenticated with bearer JWT:

EndpointReturns
GET /api/v1/reports/alertsAI Insights alert summary
GET /api/v1/reports/documentsDocument inventory (NFT metadata + event metadata + certificates)
GET /api/v1/reports/data-referencesData references report (cross-system pointer audit)
GET /api/v1/reports/supplier-performanceAggregated per-organization performance metrics
GET /api/v1/reports/production-yieldsYield aggregation by process/lot
GET /api/v1/reports/inventory-by-locationInventory grouped by custodian

These are generic aggregations useful for internal dashboards, BI, operational monitoring. Not regulatory compliance bundles.

Framework regulatory bundles

Section titled “Framework regulatory bundles”

Framework-formatted regulatory bundles are produced by a dedicated reporting service that consumes the canonical event stream:

FrameworkAvailability
FSMA 204 (CTE / KDE / TLC)Available via POST /api/v1/reports/fsma204.
EUDR DDSAvailable on demand.
USMCA Certificate of OriginAvailable on demand.
IATF 16949 quality recordsAvailable on demand.
ESPR Digital Product PassportAvailable on demand.

If your integration needs an on-demand bundle activated for your tenant, contact the team at tech@darwinevolution.io.

Generating an operational report

Section titled “Generating an operational report”

Set BASE_URL to the API base URL provided in your provisioning email.

Ventana de terminal
# Example: inventory by location
curl "$BASE_URL/api/v1/reports/inventory-by-location" \
  -H "Authorization: Bearer $TOKEN"


# Example: supplier performance
curl "$BASE_URL/api/v1/reports/supplier-performance" \
  -H "Authorization: Bearer $TOKEN"

For exact response schemas, see Reference (auto-generated from the OpenAPI spec).

How bundles are built

Section titled “How bundles are built”

Each framework has a mapping from canonical events to required data points. Mapping logic codifies regulatory expertise:

  • For FSMA 204: which captured events qualify as CTEs, which fields qualify as KDEs, how to assemble the TLC trail.
  • For EUDR DDS: which plot-level GPS data points satisfy geolocation, how to chain back to the import.
  • For USMCA: how the BOM-by-origin is computed from the multi-tier custody graph.
  • For IATF 16949: which QC records map to PPAP / FAI / SPC.
  • For ESPR DPP: how composition + recyclability + footprint flow into the JSON-LD passport.

What’s public, what’s gated

Section titled “What’s public, what’s gated”

The endpoint list and availability is public (this page). The mapping logic per framework is gated. It encodes regulatory and domain expertise.

Compliance mapping logic

The exact transformation logic from canonical events to regulatory bundles per framework, custom mapping for regulations not yet listed, and traceability of specific data points in our bundles back to your captured events. Talk to us and we'll walk through your specific compliance posture.

Talk to us →

Vertical-specific deep dives

Section titled “Vertical-specific deep dives”

For full chain examples per vertical:

  • Food traceability: FSMA 204 + EUDR end-to-end
  • Automotive: USMCA + IATF 16949 end-to-end
  • Textiles: ESPR DPP + RWS + OEKO-TEX end-to-end
Section titled “Cross-links”