Skip to main content
GET
Get LCA Dashboard
Retrieve the calculated environmental impact results for a specific LCA, organized by EN 15804 life cycle stages (A1–A4, B6, B7). Each stage contains impact values across all selected impact categories.

Request

Path Parameters

uuid
required
The UUID of the LCA portfolioExample: a1b2c3d4-e5f6-7890-abcd-ef1234567890

Headers

string
required
Your API key for authenticationExample: sk_live_1234567890abcdef
string
required
Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Query Parameters

string
default:"system"
Allocation view for co-product LCAs.Available values:
  • system — Total system impact (default)
  • product_total — Impact allocated to a specific co-product (requires output_product_id)
  • product_unit — Per-unit impact of a co-product (requires output_product_id)
uuid
UUID of the output product for co-product allocation views (product_total or product_unit). Required when view is not system.Example: bf800281-bcc7-42f4-81e4-8ec9abb9745e

Response

object
LCA metadata and dashboard configuration
array[object]
Array of life cycle stage results
boolean
Whether the results may be outdated and need recalculation.true means the impacts returned here are the previous ones: the LCA changed while they were being recalculated, so that recalculation was discarded. Nothing is wrong with the values — they are the last consistent ones — but they do not yet reflect the latest edits. Read this endpoint again, or call POST /lca/portfolio/{lca_id}/recalculate to force a full recalculation.An LCA that simply has no completed product chain yet is not reported here: that is an unfinished LCA rather than a stale one, and it surfaces through validation_errors.GET /lca/portfolio/{lca_id}/block-impacts reports its own is_stale for the same reason. The two endpoints are separate requests, so use the flag that came back alongside the numbers you are displaying.
boolean
Whether a deferred recalculation is still running.Product-use (B6/B7) and end-of-life (C4) edits hand their recomputation to an async job. While that job works, impacts_pending is true: the numbers returned are the previous ones, they will change on their own, and there is nothing to ask for. Show progress, not a call to action.Distribution and transport do not set this flag — their own /status endpoints report those operations.It is not the same as is_stale. Stale means a recalculation was discarded because the LCA changed while it was being computed; pending means one is under way. Both can be true at once — they have different causes, and each is evaluated across all of the LCA’s blocks. When they are, treat impacts_pending as the more useful thing to show: something is happening and the numbers will move on their own.Reported on block-impacts too, for the same reason is_stale is.
array[object]
Structural validation issues detected before calculation
array[object]
Warnings from the calculation engine (e.g., missing emission factors)

Example

Successful Response

Co-Product Allocation Example

For LCAs with multiple output products, use the view and output_product_id parameters to see allocated impacts:

Common Errors

404 Not Found

Cause: LCA does not exist or does not belong to the specified organization

422 Validation Error

Cause: product_total or product_unit view requested without output_product_id

List LCA Portfolios

Retrieve all LCA portfolios

LCA Overview

LCA API introduction and concepts