API changelog

The crediting_period_start and crediting_period fields on the Project resource have been converted from datetimes to dates.

Storage Locations can now specify biomass_subsurface as the storage method on creation.

• 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.

The PATCH datapoint endpoint no longer requires a value for standard_deviation.

Storage locations are now returned in the Project Monitoring Requirements resource. In addition, they now require a latitude and longitude parameter on creation.

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 /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.

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.

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.