Carbon Footprint of Business Flight Travel API

Carbon Footprint of Business Flight Travel API

Calculate emissions from business air travel between 9,200 airports with options of RF and WTT upstream factors for carbon accounting measurements.

API description

Our Approach Explained:
This algorithm calculates the distance between two airports based on their IATA codes. The database has approx. 9,200 global airports and is regularly updated. Using the principles defined in ICAO methodology, the guidelines from UK BEIS (Department for Business, Energy and Industrial Strategy) and UK DEFRA (Department for Business, Energy and Industrial Strategy) are then applied to arrive at the footprint of that journey per-passenger in a particular class.

As the ICAO does not apply the radiative forcing (RF) multiplier (accounting for the wider climate effect of emissions arising from aircraft transport at altitude) or distance uplift factor to account for delays/circling and non-direct routes (i.e., not along the straight-line/great-circle between destinations), we have added an option for you to factor it in the calculation.

WTT (well-to-tank) emissions consist of all processes between the source of the fuel (the well) through the extraction, processing (refining), storage and delivery phases up until the point of use (the tank) in the plane before take-off. This option has been added to factor the upstream emission associated with this flight in the estimation.

Ingested Data:
IATA_AIRPORT_FROM : Mandatory. This is the three-character alphanumeric geocode of the airport from which the flight is originating.
IATA_AIRPORT_TO : Mandatory. The IATA code of flight's destination airport.
FLIGHT_CLASS : Optional. The class in which the passenger is travelling. The values are Economy, Premium, Business and First. If the entered value is blank or different from these four, an "Average" factor will be considered.
ROUND_TRIP : Optional. A "Y" would mean the passenger is travelling back to the origin from destination, in the same class. The default value is "Y".
ADD_RF : Optional. A "Y" would add radiative forcing multiplier factor in the footprint calculation, while a "N" will bypass it. The default value is "Y". 
INCLUDE_WTT : Optional. A "Y" would include the Well-to-Tank (WTT) factors to the footprint calculation, while a "N" will bypass it. The default value is "Y". 
NUMBER_OF_PASSENGERS : Optional. Default to 1, if a blank or an invalid value is entered.

API Documentation

Endpoints


This calculation is used for reporting Scope 3 emissions for individuals flying for work purposes. The footprint of a flight travel is calculated based on the distance between airports and the travelling class of the passenger. With the origin and destination as inputs and following the ICAO methodology and EPA emissions factors, we apply appropriate rules based on research by IPCC.

Our algorithm calculates the distance between two airports, the IATA codes of which have been entered. The database has approx. 9,200 global airports and is regularly updated. Using the principles defined in ICAO methodology, the guidelines from UK BEIS (Department for Business, Energy and Industrial Strategy) and UK DEFRA (Department for Business, Energy and Industrial Strategy) are then applied to arrive at the footprint of that journey per-passenger in a particular class.

As the ICAO does not apply the radiative forcing (RF) multiplier (accounting for the wider climate effect of emissions arising from aircraft transport at altitude) or distance uplift factor to account for delays/circling and non-direct routes (i.e., not along the straight-line/great-circle between destinations), we have added an option for you to include it in the calculation. Use the "add_rf" field to include this factor.

WTT (well-to-tank) emissions consist of all processes between the source of the fuel (the well) through the extraction, processing (refining), storage and delivery phases up until the point of use (the tank) in the plane before take-off. Using the "include_wtt" field will add the upstream emission associated with this flight in the estimation.

The following fields are ingested:

IATA AIRPORT CODE (FROM)
Mandatory. This is the three-character alphanumeric geocode of the airport from which the flight is originating.

IATA AIRPORT CODE (TO)
Mandatory. The IATA code of flight's destination airport.

FLIGHT CLASS
Optional. The class in which the passenger is travelling. The values are Economy, Premium, Business and First. If the entered value is blank or different from these four, an "Average" factor will be considered.

ROUND TRIP
Optional. A "Y" would mean the passenger is travelling back to the origin from destination, in the same class. A "N" would consider it as a single-way trip. Any other value other than "N" will default to this input being considered as a "Y".

ADD RF
Optional. A "Y" would add radiative forcing multiplier factor in the footprint calculation, while a "N" will bypass it. Any other value other than "N" will default to this input being considered as a "Y".

INCLUDE WTT
Optional. A "Y" would include the Well-to-Tank (WTT) factors to the footprint calculation, while a "N" will bypass it. Any other value other than "N" will default to this input being considered as a "Y".

NUMBER OF PASSENGERS
Optional. Default to 1, if a blank or an invalid value is entered.

Note: If there are two passengers in the same flight, but sitting in different classes then two separate API calls are suggested, one for each passenger.

Product Page: https://www.carbonsutra.com/api-carbon-emission-flights-travel.html
Introduction Video: https://www.youtube.com/watch?v=1G4AEtpaQCU

The spreadsheet (Google Sheets) function is explained at https://www.youtube.com/watch?v=fpnuML11zTk



                                                                            
POST https://zylalabs.com/api/2678/carbon+footprint+of+business+flight+travel+api/2783/flight+travel+estimate
                                                                            
                                                                        

Flight Travel Estimate - Endpoint Features
Object Description
iata_airport_from [Required] This is the three-character alphanumeric geocode of the airport from which the flight is originating.
iata_airport_to [Required] This is the three-character alphanumeric geocode of the flight's destination airport.
number_of_passengers [Required] Default to 1, if a blank or an invalid value is entered.
flight_class [Optional] The class in which the passenger is travelling. The values are Economy, Premium, Business and First. If the entered value is blank or different from these four, an "Average" factor will be automatically considered.
round_trip [Optional] A "Y" would mean the passenger is travelling back to the origin from destination, in the same class. A "N" would consider it as a single-way trip. Any other value other than "N" will default to this input being considered as a "Y".
add_rf [Optional] A "Y" would include radiative forcing multiplier factor in the footprint calculation, while a "N" will bypass it. Any other value other than "N" will default to this input being considered as a "Y".
include_wtt [Optional] A "Y" would add the Well-to-Tank (WTT) factors to the footprint calculation, while a "N" will bypass it. Any other value other than "N" will default to this input being considered as a "Y".
cluster_name [Optional] This is an optional text field use to group the estimates into clusters which can retrieve later.
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {
  "data": {
    "type": "estimate-travel-flight",
    "iata_airport_from": "DXB",
    "airport_from": "Dubai International Airport",
    "iata_airport_to": "LAX",
    "airport_to": "Los Angeles International Airport",
    "flight_class": "Business",
    "round_trip": "Y",
    "add_rf": "N",
    "include_wtt": "N",
    "number_of_passengers": "1",
    "co2e_gm": 5777834,
    "co2e_kg": 5777.83,
    "co2e_mt": 5.78,
    "co2e_lb": 12737.8
  },
  "success": true,
  "status": 200
}
                                                                                                                                                                                                                    
                                                                                                    

Flight Travel Estimate - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/2678/carbon+footprint+of+business+flight+travel+api/2783/flight+travel+estimate?iata_airport_from=lko&iata_airport_to=maa&number_of_passengers=2' --header 'Authorization: Bearer YOUR_API_KEY' 

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Carbon Footprint of Business Flight Travel API REST API, simply include your bearer token in the Authorization header.

Headers

Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.


Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

🚀 Enterprise
Starts at $10,000/Year

  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.

Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]

Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further

Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.

Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.

You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]

 Service Level
100%
 Response Time
1,039ms

Category:


Tags:


Related APIs