Changelogs
API Releases
Classifications v2 (preview)

Classifications v2 Changelog & Upgrade Guide

Climatiq is developing a new version of the classifications endpoint. This document serves as the changelog and upgrade guide for the upcoming version. For details on how API versioning works at Climatiq, refer to our API versioning guide.

Overview

We are introducing a new major version of our classifications endpoint. This version updates the data from version 6 (opens in a new tab) to version 13 (opens in a new tab). We recommend all users transition to v2 as soon as it exits the preview phase.

Classifications v2-preview1

Classifications v2-preview1 is the initial preview version of classifications v2. Below are the key updates in v2-preview1.

Deprecation of GHG Protocol Data

The most significant change in this version is the deprecation of the GHG protocol emission factor dataset (opens in a new tab). This change is due to the upgrade from data version 6 (opens in a new tab) to version 13 (opens in a new tab). The v2-preview1 endpoint continues to support ISIC classification codes, but the calculations now rely on alternative data sources using mappings according to the UN correspondence tables (opens in a new tab).

Improved Traversal of NAICS Codes

The North American Industry Classification System (NAICS) (opens in a new tab) uses a hierarchical system of codes ranging from two to six digits. The EPA dataset (opens in a new tab) utilized by Climatiq contains emission factors only for six-digit NAICS codes, representing the most granular level of activities. In the previous version, Climatiq only accepted requests with six-digit NAICS codes. Version 2 is more flexible and accepts NAICS codes of any length, by traversing down the hierarchy and finding emission factors for any relevant child nodes.

API Changes (Request and Response)

The structure of API requests and responses remains largely unchanged. Apart from the data deprecation listed above, your requests should continue to function as before.

We encourage users to familiarize themselves with these updates and begin preparing for the transition to v2. If you have any questions or need further assistance, please refer to our documentation or contact our support team.