Attribution allows partial allocation of a CO₂e flux to a particular removal. In many cases, attribution can be handled automatically by Certify’s allocation rules, however more custom attribution strategies can be implemented using the API.

The user guides on attributing components and project emissions give a useful general introduction to concepts covered in the rest of this page.

​
Attribution datapoints

An attribution at removal or project level is defined by a datapoint with a value between 0 and 100 which determines what percentage of a component’s total value should be included.

To create an attribution factor datapoint, call the Post Datapoint endpoint with a request as follows:

Create attribution datapoint
{
  "display_name": "Attribution factor",
  "description": "Attribution factor of 50%",
  "project_id": "prj_1CTWZQGKE1S0VAXA",
  "quantity": {
    "magnitude": 50,
    "standard_deviation": null,
    "unit": "percent"
  },
  "source_ids": [
    "src_1EBBF4M7X1S06G1Y"
  ],
  "supplier_reference_id": "supplier-name-attribution-factor-50",
  "type": "REPORTED"
}

Instead of percentages, a fraction between 0 and 1 can also be used for the magnitude. In this case the unit parameter should be dimensionless.

​
Attribution within a removal

To add a new project operation component with partial attribution to a removal, first create the component and the attribution datapoint and then call the Patch Removal endpoint with a request as follows:

Patch removal
{
  "add_components": [
    {
      "attribution_factor_datapoint_id": "dtp_1DVKHKS101S0Q61Q",
      "component_id": "cmp_1EP2SB7MZ1S036PY",
      "removal_template_group_id": "rtg_1EGQ9DZXZ1S05S28"
    }
  ]
}

​
GHG Statement level attribution

Emissions can be added to a GHG statement if they relate to that reporting period. In the case that a statement has multiple removals, the emission will be automatically split evenly across all removals.

The component can be created and attributed in the same request to Post GHG Statement Component. Note that no attribution datapoint is needed in this case as attribution is calculated automatically.

Add a GHG statement level emission
{
  "component_data": {
    "activity_completed_at": "2023-11-07T05:31:56Z",
    "activity_started_at": "2023-11-07T05:31:56Z",
    "component_blueprint_key": "<string>",
    "description": "<string>",
    "display_name": "<string>",
    "inputs": [
      {
        "__typename": "CreateComponentListInput",
        "datapoint_ids": [
          "dtp_1DVKHKS101S0Q61Q"
        ],
        "input_key": "<string>"
      }
    ],
    "project_id": "prj_1CTWZQGKE1S0VAXA",
    "supplier_reference_id": "<string>"
  },
  "ghg_statement_id": "ggs_1GDQJ99Z51S0DYW9"
}

​
Attribution of project emissions

Project emissions can be automatically allocated by Certify using an allocation rule. If a Manual allocation rule is selected, suppliers can define their own allocation strategy using API updates to amend removals.

Once a project emission, attribution datapoint and removal has been created, the emission can be attributed by calling the Post Project Component Removal Attribution endpoint:

Attribute project emission to removal
{
  "attribution_factor_datapoint_id": "dtp_1DVKHKS101S0Q61Q",
  "removal_id": "rmv_1EEM6NJXX1S0EXKD"
}

The project emission component ID is specified as a path parameter in the request.

​
Full attribution

Components cannot be attributed beyond 100%. In the event a request is sent attempting to over-attribute a component, the API will respond with a 400 error.