Welcome to the Certify API changelog. For the overall product changelog, please see here.

​
2025

​
2025-06-27
Associating feedstocks to Projects
Project ID is now required when creating a feedstock type. It has been added to the body of the feedstock type creation request.
​
2025-06-18
Deprecating measurement location on datapoints
Measurement location is being removed from the measurement location resource. It has been removed from the body of the datapoint creation request. It will be removed from the body of the datapoint response at a future date.
​
2025-06-12
Crediting period dates have been converted from datetimes to dates
The crediting_period_start and crediting_period fields on the Project resource have been converted from datetimes to dates.
​
2025-05-29
Subsurface storage method supported
Storage Locations can now specify biomass_subsurface as the storage method on creation.
​
2025-05-22
Storage Unit endpoint + Storage Locations on Measurement Samples.
  • Endpoints for managing storage units were released in beta. See GET Storage Unit for details.
  • Storage Locations can now also be attached to Measurement Samples on creation.
​
2025-05-21
Standard deviation value optional on PATCH datapoint
The PATCH datapoint endpoint no longer requires a value for standard_deviation.
​
2025-05-14
Storage Locations returned on monitoring requirement resource and location required
Storage locations are now returned in the Project Monitoring Requirements resource. In addition, they now require a latitude and longitude parameter on creation.
​
2025-04-29
Storage method field added to Storage Location
Storage locations now require a storage_method parameter on creation.See POST Storage Location for details.
​
2025-04-25
Measurement Sample endpoints added
Measurement samples can now be created and fetched via the Certify API.See POST Measurement Samples for details.
​
2025-04-16
Process resource deprecated in favour of Removal Template
LCA templates built in Certify can be now retrieved at GET /projects/{project_id}/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.
​
2025-02-28
Project-scoped components now accept time-based allocation strategies
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.
​
2025-02-04
Removals now allow assignment of labels
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.
​
2025-01-24
Project-scoped components now require an allocation strategy
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-12-13
Datapoints are now associated to projects
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.