Once you have confirmed you can access the API, have created a project and built your LCA, you can start submitting removal data.

The process of uploading removal data is described in the sequence below:

1

Create Sources

Sources are documents that support the data you are uploading. They are created by using the POST source endpoint creating a resource in the Isometric system then uploading the document to the signed upload URL we return.

2

Create Datapoints

Datapoints are values that are used in the carbon accounting calculations. They are created using the POST datapoint endpoint. Source IDs representing the sources that support the datapoint can be passed in.

3

Optional: Create feedstock type

Feedstock types represent a single type of feedstock used in a removal. Feedstock types should be created if the removal uses a feedstock that is not already in the system. The feedstock type can be created using the POST feedstock type endpoint.

4

Create removal

Removals represent a combination of activities that result in CO₂e being removed from the atmosphere. A removal is created from a Removal Template using the POST removal endpoint. The template specifies which groups, components and fixed input datapoints the removal will be created with. At this step only datapoints for monitored inputs need to be submitted, fixed input datapoints will be inherited from the removal. Removal templates and their inputs are available to query through the API using the GET removal templates endpoint.

5

Optional: Customize removal

Removals might need to differ from your removal template on a case-by-case basis to match your operational activities. Individual components can be created with the POST component endpoint, and then attributed to the removal using the PATCH removal endpoint. Unneeded components can also be removed from a removal using the same endpoint.

Components represent physical activities whose CO₂e flux needs to be accounted for. Components are created from component blueprints that define the calculations of a transfer of CO₂e into or out of the atmosphere, and all the necessary datapoint inputs required for this calculation.

6

Create GHG statement

A GHG statement represents a set of removals that will be verified together. It can be created in the Isometric system using the POST GHG statement endpoint. After verification, credits will be issued for all removals in a GHG statement at the same time.

To prevent overlaps in reporting periods, GHG Statements in the Isometric system must be contiguous. When creating one, we will ask you to provide its end date, and the start date will be automatically inferred from the previous GHG statement if one exists, or the earliest removal in the project. All removals with a completed_at date within the GHG statement period will be included in the statement.

7

Submit GHG statement for verification

Once you have added all the removals to a GHG statement, you can submit it for verification using the submission endpoint. The verifier will be able to see all the resources associated with the removals once it is submitted.