2025
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 removal 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.