Emission Calculations

Calculate the emission footprint of your transportation movements.

The POST TransportEmissions endpoint provides access to detailed emissions data related to transportation activities within the FincoEnergies platform. This endpoint is crucial for tracking and managing the environmental impact of your transportation and distribution operations. The emissions data retrieved through this endpoint is calculated based on the Global Logistics Emissions Council (GLEC) framework, an internationally recognized standard for measuring and reporting logistics emissions (ISO14083).

By using this endpoint, you can obtain accurate and standardized emissions data that aligns with global sustainability practices, helping you to monitor and reduce your carbon footprint effectively. This information is vital for companies committed to sustainability and transparency, enabling them to report emissions accurately and make informed decisions to minimize environmental impact.

Default request:

Parameters

• No parameters needed

Request body (mandatory fields):

{
  "BatchID": "string"
  "TransportMode": "Seaship",
  "FreightWeight": 0,
  "WeightUnitOfMeasurement": "teu",
  "Reefer": true,
  "OriginCityName": "string",
  "OriginCountryCode": "string",
  "DestinationCityName": "string",
  "DestinationCountryCode": "string"
}

• BatchID - optional field, adds a unique identifier to your emission calculation. 
• TransportMode - choose 'Train', 'Truck', 'Inland', 'Seaship' or 'Airplane'.
• FreightWeight - choose a number, e.g. 20.
• WeightUnitOfMeasurement - choose 'teu' (20ft container), 'feu' (40ft container), 'kg' or 'ton' (1.000 kg).
• Reefer - Indicates whether cooled transportation applies, choose True or False.
• OriginCountryCode - the country code of the origin; choose from the list Appendix C (below).
• DestinationCountryCode - the country code of the destination; choose from the list Appendix C (below).
• OriginCityName - choose the city name of the origin (tip: avoid region names, symbols and characters other than the qwerty keyboard). 
• DestinationCityName - choose the city name of the destination (tip: avoid region names, symbols and characters other than the qwerty keyboard). 

Request body (optional, advanced fields):

"AdvancedSettings": {
        "OriginUNLOCODE": "NLRTM",
        "DestinationUNLOCODE": "USLGB"
    }

In case the user wishes to calculate emissions for a specific port, one can add the UN/LOCODE of the port. Note: these fields overwrite the "OriginCityName" and "DestinationCityName". 

• "OriginUNLOCODE": The UN/LOCODE of the origin port, e.g. NLRTM = NL, Rotterdam. 
• "DestinationUNLOCODE": The UN/LOCODE of the destination port, e.g. USLGB = US, Long Beach. 

"AdvancedSeaSettings": { 
        "LoadFactor": 60, 
        "SeaCargoType": "Container" 
}

The "LoadFactor" defines how much % of the container is actually being used for cargo. If the loadFactor is high, the emissions of the TEU are shared across more cargo, and therefore lower. Vice-versa also applies: a lower loadFactor of the TEU leads to more emisisons per TEU. Use a value between 1 (for 1%) and 100 (for 100%).  

The "SeaCargoType" can be used to specifiy the vessel type. Please use one of the following options:

• "BulkCarrier"
• "ChemicalTanker"
• "Container"
• "GeneralCargo"
• "Liquid"
• "OilTanker"
• "Ferry"
• "RoRo"
• "Vehicle"

2. For road transpotation (TransportMode = "Truck")

"AdvancedRoadSettings": {
        "OriginZIPCode": "1031AP",
        "DestinationZIPCode": "1100DL",
        "TruckType": "Class40",
        "TruckBodyType": "car"
        "EmissionClass": "EuEuro6",
        "FuelType": "hvo",
        "EmptyRunFactor": 70
  }

In case the user wishes to calculate intra-city emissions (e.g. from London to London), one can add the zip codes. Note: these fields overwrite the "OriginCityName" and "DestinationCityName", but do need to be used in combination with the "OriginCountryCode" and "DestinationCountryCode".

• "OriginZIPCode": concerns the zip code of the origin, e.g. 1013AP.
• "DestinationZIPCode": concerns the zip code of the destination.

For "TruckType", the vehicle type can be specified. The options are summarized in Appendix A.

For "TruckBodyType", the user can specify a truck body type. The following options are available.

• "curtainsider" - Curtain Sider Trailer
• "cargobox" - Trailer with a fixed body (e.g. wood or metal)
• "cooledbox" - Container chassis
• "tank" - Tanker truck
• "car" - Car transporter truck
• "container" - Container chassis truck for a single TEU
• "container2TEU" - Container chassis truck for two TEU or one FEU. 

For "EmissionClass", the user can specify the emission class used. The options are summarized in Appendix B.

For "FuelType", the default value is "diesel 100%". The user can use the following options to overwrite the default option:

• "hvo"
• "electricity"

For "EmptyRunFactor", simulates how much of the return trip is empty, with a value between 0 and 100. For example, EmptyRunFactor = 50 assumes that half of the return trip is empty. Default value is 0% (no empty return assumed). 

-----

3. For air transportation (TransportMode = "Airplane"):

"AdvancedAirSettings": { 
        "AircraftType": "string" 
}

With "aircraftType", user can specify the aircraft type, e.g. HybSH (hybrid short haul), HybMH (hybrid medium haul) or HybLH (hybrid long haul). 

Responses: 

200: Default response:

{
  "CO2eTons": 6.2315752
}

422: Validation error response:

{
  "message": "cvc-enumeration-valid: Value 'seaship' is not facet-valid with respect to enumeration '[Train, Truck, Inland, Seaship, Airplane]'. It must be a value from the enumeration. cvc-type.3.1.3: The value 'seaship' of element 'TransportMode' is not valid."
}

500: Default error response:

{
  "error": "Description of the error(s) that occurred."
}

504: Timeout error response:

{
  "error": "Timeout waiting for response"
}

Appendix A: VehicleType (for trucks):

Appendix B: EmissionClass (for trucks)

Appendix C: Country codes