Travel ADD-ONADD-ON

Climatiq provides a comprehensive toolkit to help businesses measure GHG emissions from travel activities. This includes reporting scope 3.6 emissions under the GHG Protocol for travel activities in vehicles owned or operated by third parties, such as aircraft, trains and passenger cars. Emissions associated with hotel stays can also be calculated, providing a comprehensive view of travel-related emissions.

The GHG Protocol outlines three main methods for calculating GHG emissions from your travels:

• Fuel-based
• Distance-based
• Spend-based

Your choice of method will depend on the data you have at hand.

Our endpoints are tailored to handle all possible situations with respect to your data availability. Use our spend-based endpoint if you only have expenditure data available. For enhanced accuracy, the distance-based endpoint offers route-specific estimates, automatic distance calculations, and customization options to improve calculations.

Distance-based method

POST This endpoint allows you to apply the distance-based method by specifying the origin and destination of your journey, and the primary mode of transportation: by air, car, or rail. The journey distance is automatically determined and used for the calculation.

The endpoint will return the CO2e for the primary mode of transportation. If the journey includes separate legs (e.g. travel to / from a railway station or airport) then these need to be calculated separately with additional calls to the API.

https://preview.api.climatiq.io/travel/v1-preview1/distance

Request

Car Sizes

The car_details object allows you to specify different car types that you can see in the list below. If you don't know the size of the car used for the trip, you can omit the car_size or set it as average, both of which will result in a weighted average of car sizes on the road being used.

curl --request POST \
  --url https://preview.api.climatiq.io/travel/v1-preview1/distance \
  --header "Authorization: Bearer $CLIMATIQ_API_KEY" \
  --data '{
    "origin": {
        "locode": "DE-HAM"
    },
    "destination": {
        "query": "Berlin"
    },
    "travel_mode": "car",
    "car_details": {
        "car_type": "plugin_hybrid"
   }
}'

Response

A response consists of the following attributes.

{
    "co2e": 45.27,
    "co2e_unit": "kg",
    "distance_km": 305.8,
    "origin": {
        "name": "Hamburg",
        "latitude": 53.516666666666666,
        "longitude": 9.933333333333334,
        "confidence_score": null
    },
    "destination": {
        "name": "Berlin, Germany",
        "latitude": 52.51604,
        "longitude": 13.37691,
        "confidence_score": 1
    },
    "direct_emissions": {
        "co2e": 35.03,
        "co2e_unit": "kg"
    },
    "indirect_emissions": {
        "co2e": 10.24,
        "co2e_unit": "kg"
    },
    "notices": []
}

Spend-based method

POST This endpoint uses EXIOBASE emission factors to calculate emissions based on your spending on travel activities in any currency. This endpoint automatically takes inflation into account, if the year you spent the money was different than the year of the emission factor. Note that the EXIOBASE spend-based emission factor, used for the road travel is, in fact, an average emission factor for a mix of different types of transport: urban and suburban passenger land transport, taxi operation, other passenger land transport and freight transport by road and can therefore produce results of lower accuracy. Climatiq advises to use fuel-based or distance-based method, where possible.

https://preview.api.climatiq.io/travel/v1-preview1/spend

Request

curl --request POST \
  --url https://preview.api.climatiq.io/travel/v1-preview1/spend \
  --header "Authorization: Bearer $CLIMATIQ_API_KEY" \
  --data '{
    "spend_type": "air",
    "money": 100,
    "money_unit": "gbp",
    "spend_location": {
        "locode": "GB-LON"
    },
    "spend_year": 2018
}'

Response

{
    "co2e": 135.5,
    "co2e_unit": "kg",
    "spend_location": {
        "name": "London, LND, GB",
        "confidence_score": null
    },
    "notices": []
}

Hotels

POST Use this endpoint to estimate emissions from hotel stays across the world based on the number of nights spent. If no emission factor is available for hotels in the given country, another factor from the same continent is used.

https://preview.api.climatiq.io/travel/v1-preview1/hotel

Request

curl --request POST \
  --url https://preview.api.climatiq.io/travel/v1-preview1/hotel \
  --header "Authorization: Bearer $CLIMATIQ_API_KEY" \
  --data '{
    "hotel_nights": 5,
    "location": {
        "query": "San Francisco"
    }
}'

Response

{
    "co2e": 80.5,
    "co2e_unit": "kg",
    "location": {
        "name": "United States",
        "confidence_score": 1
    },
    "notices": []
}

Location

Many of the endpoints accept a location. There are four different ways to input a location.

Query Location

All the properties are optional, but you must specify at least a query or a country + postal_code. You may specify all three. Note that not all countries have support for postal codes, and the format might be different from country to country. See this table (opens in a new tab) for details on postal codes.

IATA Code Location

UN/LOCODE Location

Coordinate Location

Response Location

The location that is returned to you in the API response will contain the following properties

Notices

The notices array can contain these objects:

The different possible values for code are as follows. You should not treat this list as exhaustive as more values may be added with time: