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.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
.location_id
no longer gets returned on datapoints, instead it is an attribute on the measurement sample resource.
See GET measurement samples
.project_id
is now required when creating a feedstock type.
It has been added to the body of the POST feedstock type
request.POST datapoint
request and will be removed from the body of the datapoint response at a future date.crediting_period_start
and crediting_period
fields on the GET projects
resource have been converted from datetimes to dates.biomass_subsurface
as the storage method on POST storage location
.GET storage unit
for details.POST measurement samples
.PATCH datapoint endpoint
no longer requires a value for standard_deviation
.GET project monitoring requirements
resource. In addition, they now require a latitude
and longitude
parameter on POST storage location
.storage_method
parameter on creation.See POST storage location
for details.POST measurement samples
for details.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.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.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.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.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.