This endpoint returns CO2e emissions (i.e CO2 equivalent emissions) in grams (g) for the shortest path between a port of origin (from) and a port of destination (to).

Origin and destination

You must provide either fromLocode or fromCoordinates for the origin and either toLocode or toCoordinates for the destination.
You can use the parameter distance (in meters) to pass your own distance (the origin and destination remain mandatory because the co2 computation is region dependent).

Vessel information

You can obtain accurate CO2 values for a specific vessel by passing its IMO as a query parameter. If we cannnot find enough data on the IMO you passed as a parameter, if you pass a wrong IMO number or if you pass no IMO, we estimate the CO2e emissions based on the trade lane (with 30 trade lanes supported) using the GLEC coefficients.

Fuel types

When a vessel IMO number is provided, we use its fuel type for emission factors, taking into account if necessary fuel switches within SECA zones (ie VLSFO -> LSMDO).
Presence of a scrubber is also taken into account for emissions within SECA zones.

If the fuel type for the vessel is missing from our dataset, we will use VLSFO as default value since it is IMO 2020 compatible. The optional customer parameter fuelType will overwrite the vessel’s default fuel if it is physically compatible with the structure of the vessel.
For example, ULSFO or UCO for ships running on HFO, or VLSFO or BIOLNG for LNG ships using dual engines will be taken into account, but METHANOL for a HFO vessel will not.
The fuel type taken into account for CO2 calculation is specified in the response (fuelType in properties).

When no IMO number is provided, the response will use GLEC emission factors and fuelType parameter will not have an impact on the result.

Cargo specifications (container only)

We provide CO2 calculation for FCL and LCL. We support dry and reefer container types (containerSizeTypeCode).
The following types are supported by our API :
20GP, 22G1, 2200, 22G0, 2202, 2210 (20ft, General purpose (Standard)) [Default]
40GP, 42G1, 42G0, 40G1 (40ft, General purpose (Standard)),
40HC, 45G1, 45G0, 4500, 4510 (40ft High cube, General Purpose),
22R1, 2231 (20ft, Reefer),
40NOR, 42R1, 4531 (40ft, Reefer),
40REHC, 45R1, 45R8 (40ft High cube, Reefer),
53GP (53ft High cube).

Routing parameters

Avoid zones

ECA zones can be avoided by using the parameter avoidSeca. In that case, the distance travelled in the ECA zone is minimized.
The HRA (high risk area) zone can be avoided using parameter avoidHRA. If no points from the query are in the HRA zones, the zone will be totally avoided, if at least one point is in the HRA zone, the route will go through it but minimize the distance navigated in it.

Ice areas and block areas

By default, the seas that are difficult to sail due to the presence of ice are not allowed (for example the Bering Sea, the Northern Sea Route, etc). You can allow the route to go through these zones by using the allowIceAreas parameter.
It is possible to block some areas by using the parameter blockAreas which takes a list of ids (Panama Canal : 11112 , Suez Canal : 11117). In that case, the route won't cross the areas blocked.

Impact of the weight and number of containers on CO2e emissions and intensity calculation

For CO2e emissions:

The CO2e emissions only depend on the number of containers (nContainers). If you don't know the nContainers but you know the total weight of the goods, our algorithm will estimate the nContainers based on the weight.
If neither nContainers nor weight are provided, by default, we return emissions for one TEU (20G1, Dry).

For CO2e intensity:

The CO2e intensity depends on the weight. If you don't know the weight but you know the nContainers, our algorithm will estimate the weight based on the nContainers.

Note that you can give a non integer number of containers that allows you to calculate CO2e for LCL.


The response contains CO2e WTW (well-to-wheels) emissions in grams (g) for the shortest route between origin and destination ports. We also provide detailed emissions with TTW (tank-to-wheels) emissions and WTT (well-to-tank) emissions. The method takes into account the emissions caused by the fuel consumption of the main engines, the auxiliary engines and the boilers.

The response also returns the intensity factor (kg of CO2e per ton.kilometer) which is calculated based on the CO2e WTW, distance and the weight provided. If no weight has been provided, we estimate the weight based on the number of containers and their type (weight in properties)

The parameters field in the response contains all the parameters that were given in the request.

The properties field in the response gives some data that was used to calculate the CO2 based on the parameters for example the distance, the distance in ECA zones, some data about the vessel, the trade lane, etc. The property dataType precise if the data used to calculate the CO2 emissions is default data (representative of average operating practices) or modeled data (taking into account vehicle information).

Note that the distance we use to calculate CO2e is 15% higher than the shortest distance (returned in the response in meters (m)) as recommended by the GLEC framework to take into account the stops in other ports, the weather and all other deviations from the shortest route.

Methodology references

The method used to calculate emissions is based on the following references:

  • Third IMO Greenhouse Gas Study 2014;
  • Fourth IMO Greenhouse Gas Study 2020;
  • EMEP/EEA air pollutant emission inventory guidebook 2019;
  • GLEC Framework 2020.
Click Try It! to start a request and see the response here!