> ## Documentation Index
> Fetch the complete documentation index at: https://docs.isometric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating your first GHG entry

Once you have confirmed you can [access the API](/api-reference/introduction#request-access), have
[created a project](/user-guides/certify/create-project) and
[built your LCA](/user-guides/certify/lca), you can start submitting GHG entry data.

<Info>
  Prefer the `ghg_entry*` and `ghg_entry_template*` endpoints documented below. The older
  `removal*` and `removal_template*` endpoints remain available as deprecated compatibility
  aliases while existing integrations migrate.
</Info>

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

<Steps>
  <Step title="Create Sources">
    Sources are documents that support the data you are uploading.
    They are created by using the [POST source endpoint](/api-reference/certify/post-source)
    creating a resource in the Isometric system then [uploading the document](/api-reference/certify/uploading-sources) to the signed upload
    URL we return.
  </Step>

  <Step title="Create Datapoints">
    Datapoints are values that are used in the carbon accounting calculations.
    They are created using the [POST datapoint endpoint](/api-reference/certify/post-datapoint).
    Source IDs representing the sources that support the datapoint can be passed in.
  </Step>

  <Step title="Optional: Create feedstock type">
    Feedstock types represent a single type of feedstock used in a GHG entry.
    Feedstock types should be created if the GHG entry uses a feedstock that is not already in the
    system.
    The feedstock type can be created using the
    [POST feedstock type endpoint](/api-reference/certify/post-feedstock-type).
  </Step>

  <Step title="Create GHG entry">
    GHG entries represent a combination of activities that result in CO₂e being removed from the
    atmosphere or reduced relative to a baseline.
    A GHG entry is created from a *GHG Entry Template* using the
    [POST GHG entry endpoint](/api-reference/certify/post-ghg-entry).
    The template specifies which groups, components and fixed input datapoints the GHG entry will be
    created with.
    At this step only datapoints for
    [monitored inputs](/user-guides/certify/component-blueprint-library#fixed-and-monitored-inputs)
    need to be submitted; fixed input datapoints will be inherited from the template.
    GHG entry templates and their inputs are available to query through the API using the
    [GET GHG entry templates endpoint](/api-reference/certify/get-ghg-entry-templates).
  </Step>

  <Step title="Optional: Customize GHG entry">
    GHG entries might need to differ from your template on a case-by-case basis to match your
    operational activities.
    Individual components can be created with the
    [POST component endpoint](/api-reference/certify/post-component), and then attributed to the
    GHG entry using the [PATCH GHG entry components endpoint](/api-reference/certify/patch-ghg-entry-components). Unneeded
    components can also be removed from a GHG entry using the same endpoint.

    <Info>
      Components represent physical activities whose CO₂e flux needs to be accounted for.
      Components are created from
      [component blueprints](/user-guides/certify/component-blueprint-library) 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.
    </Info>
  </Step>

  <Step title="Create GHG statement">
    A GHG statement represents a set of GHG entries that will be verified together.
    It can be created in the Isometric system using the
    [POST GHG statement endpoint](/api-reference/certify/post-ghg-statement).
    After verification, credits will be issued for all GHG entries in a GHG statement at the
    same time.

    <Info>
      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 GHG entry
      in the project. All GHG entries with a `completed_on` date within the
      GHG statement period will be included in the statement.
    </Info>
  </Step>

  <Step title="Submit GHG statement for verification">
    Once you have added all the GHG entries to a GHG statement, you can submit it for verification
    using the [submission endpoint](/api-reference/certify/post-ghg-statement-submit).
    The verifier will be able to see all the resources associated with the GHG entries once it is
    submitted.
  </Step>
</Steps>