2026
The Removal entity has been deprecated in favour of GHG Entry in order to support reporting for multiple credit types. As a result, Certify’s REST API now exposes a new
ghg_entry and ghg_entry_template route family across the main carbon accounting flows. This is primarily a naming update of the existing removal-named API surface, making the terminology consistent with GHG entries and GHG entry templates without substantially changing the underlying integration flow.New endpoints are now available for listing and retrieving templates, creating and managing entries, and working with entry component attribution. This includes GET ghg entry templates, GET ghg entry template, GET datapoint ghg entry template components, GET ghg entries, GET ghg entry, POST ghg entry, PATCH ghg entry, DELETE ghg entry, GET ghg entry components, and PATCH ghg entry components.Project-scoped attribution has also been renamed into the same model through POST project component ghg entry attribution and DELETE project component ghg entry attribution.Alongside the new route family, related resources and filters now expose GHG entry naming throughout the API. For example, templates now include credit_type, GHG statements expose ghg_entry_ids, and related resources such as component attributions, components, and biochar applications now return GHG entry-named fields to match the new endpoints.We intend to keep old endpoints functional for a transitional period of 3 months (until September 2026), after which they will be removed. We recommend that you migrate to the new endpoints as soon as possible to ensure uninterrupted functionality.A new
DELETE measurement_samples/{id} endpoint has been added, allowing you to delete a measurement sample by its ID.A new optional
description field has been added to the Source resource. It is returned on all endpoints that return a Source entity and can be set via POST source or PATCH source.risk_of_reversal_percentage and credit_allocation have been added to the GET removal and GET removals endpoints.credit_allocation has also been added to the GET ghg_statement and GET ghg_statements endpoints, summarizing the total credit allocation across all removals in the statement.credit_allocation contains two fields: buffer_pool_contribution_kg (credits contributed to the buffer pool) and supplier_allocation_kg (credits issued to the supplier). It is null if any removal’s risk_of_reversal_percentage has not yet been set.2026-05-19
Filter datapoints by measurement sample ID; datapoint IDs added to measurement sample values
A new
measurement_sample_id query parameter has been added to the GET datapoints endpoint, allowing you to filter datapoints linked to a specific measurement sample.Additionally, each object in the values array returned by POST measurement_samples now includes a datapoint_id field.The
reporting_period_start_at and reporting_period_end_at fields have been added to the GET ghg_statements and GET ghg_statement endpoints. These fields represent the inclusive start and end dates of the reporting period.feedstock_type_id has been replaced by feedstock_batch_id in the POST measurement samples endpoint.A
project_id is now required when creating a source. It has been added to the body of the POST source request and is returned on all endpoints that return a
Source entityAdditionally, a new field original_filename has been added to Source. This field contains the original filename of
uploaded documents.Feedstock batches can now be managed via the Certify API.See
Feedstock batches for details.A new field
removal_template_component_id has been added to all endpoints that return a Component or Removal Component entity.
This helps to facilitate mapping to removal components from third-party reporting systems.2025
Storage method
dac_saline_aquifer is replaced by saline_aquifer as the storage method on POST storage location.feedstock_type_ids replaces feedstock_type_id in the POST production batch endpoint.
This field allows specifying multiple feedstock types associated with a production batch.Feedstock types can now only be created via the Certify UI and not via API.
A new field
uncertainty_justification has been added to the POST datapoint and PATCH datapoint
endpoints. This field allows providing additional context or explanation regarding the uncertainty associated with a
datapoint. It is only required when sensitivity analysis
identifies the datapoint as sensitive.A new endpoint for attributing components to removals has been added:
PATCH removal components. This new endpoint allows attributing components fully
or partially without having to create Datapoints to represent attribution. Attributing components via PATCH removal add_components & remove_components_ids is now deprecated.Similarly, POST project component removal attribution has been updated to allow attribution
with a float value. Attributing components via datapoints has been deprecated.The
GET datapoints endpoint now returns a locked_status field indicating whether the datapoint can be patched or if it is locked due to references that render it immutable.Two new endpoints have been added:
GET datapoint components retrieves components that use the specified datapoint, and GET datapoint removal template components retrieves removal template components that use the specified datapoint.The GET components endpoint has been expanded with new filter options, including scope, ghg_statement_id, project_id and removal_id.
Additionally, the GET datapoints endpoint now supports an expanded set of filters for more granular querying of datapoints including all of the above and extending to removal.Measurement
location_id no longer gets returned on datapoints, instead it is an attribute on the measurement sample resource.
See GET measurement samples.A
project_id is now required when creating a feedstock type.
It has been added to the body of the POST feedstock type request.Measurement location information is being moved from the datapoint to the measurement sample resource.
It has been removed from the body of the
POST datapoint request and will be removed from the body of the datapoint response at a future date.The
crediting_period_start and crediting_period fields on the GET projects resource have been converted from datetimes to dates.Storage Locations can now specify
biomass_subsurface as the storage method on POST storage location.- Endpoints for managing storage units were released in beta. See
GET storage unitfor details. - Storage Locations can now also be attached to Measurement Samples on
POST measurement samples.
The
PATCH datapoint endpoint no longer requires a value for standard_deviation.Storage locations are now returned in the
GET project monitoring requirements resource. In addition, they now require a latitude and longitude parameter on POST storage location.Storage locations now require a
storage_method parameter on creation.See POST storage location for details.Measurement samples can now be created and fetched via the Certify API.See
POST measurement samples for details.LCA templates built in Certify can be now retrieved at
GET removal templates. This deprecates the Process resource and simplifies the reuse of fixed inputs on removal templates.The process_key and steps fields are now deprecated on POST removals in favour of removal_template_id and removal_template_components. See creating your first GHG entry for details.The
POST project component endpoint request body now accepts two new strategies for allocation_strategy: ESTIMATED_PROJECT_LIFETIME and CUSTOM_TIME_PERIOD.
The PATCH component endpoint request body now accepts two new strategies for allocation_strategy: ESTIMATED_PROJECT_LIFETIME and CUSTOM_TIME_PERIOD.You have a choice of an ESTIMATED_PROJECT_TONNAGE, ESTIMATED_PROJECT_LIFETIME, CUSTOM_TIME_PERIOD or MANUAL allocation_strategy and can patch the choice in the future if any updates or changes occur.The
POST removal endpoint now accepts a list of label_ids in the request body.
The PATCH removal endpoint now accepts a list of label_ids field in the request body.
The GET removal endpoint now returns a list of label_ids field in the response body.Labels are currently an optional field for Removals.The
POST project component endpoint now accepts an allocation_strategy in the request body.
The PATCH component endpoint now accepts an allocation_strategy field in the request body.
The GET component endpoint now returns an allocation_strategy field in the response body.An allocation_strategy is currently a required field for all Project-scoped components.
You have a choice of an ESTIMATED_PROJECT_TONNAGE or MANUAL allocation_strategy and can patch the choice in the future if any updates or changes occur.2024
The
POST datapoint endpoint now accepts a project_id in the request body.
The GET datapoint endpoint now returns a project_id field in the response body.The project_id is currently an optional field but will become required in the future.
You should therefore ensure that you migrate your code to include the project_id in the request body.