Carbon Footprint of Business Hotel Stay API

Carbon Footprint of Business Hotel Stay API

This API calculates hotel stay carbon footprint based on country, city/region (optional), and hotel rating. It computes emission factor from over 300 cities/regions in 38 countries. Emission is determined by rooms and stay duration, providing CO2 values in kg, metric tonnes, and pounds.

CarbonSutra's approach for calculating the carbon footprint of hotel stays is based on Cornell Hotel Sustainability Benchmark Index and UK government's GHG conversion factors published in 2022. Based on country and optionally entered city or region in that country along with rating of the hotel, the emission factor is calculated. Over 300 cities and regions across 38 countries are covered. The final emission is calculated based on number of rooms taken in the hotel and the length of the stay.

The following fields are ingested:

COUNTRY CODE
Mandatory. This is a ISO 3166-1 alpha-2 code, pointing to its ISO 3166-2 article. While the list of codes is available at Wikipedia's ISO 3166-1 alpha-2 page, we are listing the 38 countries and their 2 character codes below in the footnote. [1]

CITY NAME
Optional. Enter the city within the country where the hotel is based. The algorithm will search the database for the name and if it is not found, it will search for any emission factors associated with the region in which the city is located.

HOTEL RATING
Optional. The star rating of the hotel. Enter the value of "2" for a 2-star hotel. Similarly, "3", "4" and "5" will match the corresponding rating of the hotel. If this is not known then leave it as blank.

NUMBER OF NIGHTS
Optional. This is the length of the stay in the hotel. The default value is 1.

NUMBER OF ROOMS
Optional. The number of rooms taken in the hotel. The default value is 1. Note that the number of travelers staying in the same room do not matter.

Product Page: https://www.carbonsutra.com/api-carbon-emission-hotel-stay.html
Introduction Video: https://www.youtube.com/watch?v=2isL9LwL7r0

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

[1]: Countries and ISO codes used in this API: Australia (au), Belgium (be), Brazil (br), Canada (ca), Chile (cl), China (cn), Colombia (co), Costa Rica (cr), Egypt (eg), France (fr), Germany (de), Hong Kong (hk), India (in), Indonesia (id), Italy (it), Japan (jp), Jordan (jo), Korea (kr), Malaysia (my), Maldives (mv), Mexico (mx), Netherlands (nl), Oman (om), Philippines (ph),Portugal (pt),Qatar (qa), Russian Federation (ru), Saudi Arabia (sa), Singapore (sg), South Africa (za), Spain (es), Switzerland (ch), Thailand (th), Turkey (tr), United Arab Emirates (ae), United Kingdom (gb), United States of America (us), Vietnam (vn).

API Documentation

Endpoints


This computes the emissions from stationary combustion fuels which are burnt in a fixed unit or asset owned or controlled by the reporting organization, and usually reported as a Scope 1 direct emission. The source of data and methodology of emission factor calculation are from UK government's GHG conversion factors for company reporting and Ministry of Business, Innovation and Employment (MBIE)'s data of 2022 from New Zealand.

The following fields are accepted:

FUEL_USAGE : Mandatory. The usage of the fuel can be entered as either "commercial", "industrial", "transport" or "residential". If left blank, it will default to "commercial". Note that "commercial" is to be used for fuels used at sites or properties where commercial activities take place. "industrial" is used when combustion takes place at sites where industrial processes occur or within engines that support industrial activities. "residential" can be applied for fuel used primarily at residential properties. "transport" in this category is for the fuel used in an engine to move a vehicle.

FUEL_NAME : Mandatory. A blank value will result in an error. Described here are the fuel types (within quotes) that are to be used. They are divided into categories for ease of understanding:
Petrol: Two types of petrol can be used under the fuel_usage category of transport. They are "Premium Petrol" and "Regular Petrol".
Coal: Four ranks of coal can be used under any of the fuel_usage categories of commercial, industrial or residential. The values are: "Coal - Default", "Coal - Bituminous", "Coal - Sub-Bituminous" and "Coal - Lignite".
Diesel: Use "Diesel" under any of the fuel_usage categories of commercial, industrial or transport.
LPG: Use "LPG" under any of the fuel_usage categories of commercial, industrial or transport.
Fuel Oils: Two types of fuel oils can be used under the fuel_usage categories of commercial, industrial or transport. They are "Heavy Fuel Oil" and "Light Fuel Oil".
Natural Gas: Use "Natural Gas" under fuel_usage categories of commercial or industrial.
Aviation Fuels: Use "Aviation fuel - Kerosene" or "Aviation gas" under fuel_usage value of transport.

โ€‹FUEL_VALUE : Mandatory. A blank value will result in an error. The unit of fuel_value is fixed for the categories of fuel as per the following rules:
Petrol: "litre"
Coal: "kg"
Diesel: "litre"
LPG: "kg"
Fuel Oils: "litre"
Natural Gas: "kWh"
Aviation Fuels: "litre"




                                                                            
POST https://www.zylalabs.com/api/2689/carbon+footprint+of+business+hotel+stay+api/2795/fuel+consumption+estimate
                                                                            
                                                                        

Fuel Consumption Estimate - Endpoint Features
Object Description
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {
  "data": {
    "type": "estimate-fuel",
    "fuel_usage": "commercial",
    "fuel_name": "LPG",
    "fuel_unit": "kg",
    "fuel_value": "5600",
    "co2e_gm": 16960643,
    "co2e_kg": 16960.64,
    "co2e_mt": 16.96,
    "co2e_lb": 37391.43
  },
  "success": true,
  "status": 200
}
                                                                                                                                                                                                                    
                                                                                                    

Fuel Consumption Estimate - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/2689/carbon+footprint+of+business+hotel+stay+api/2795/fuel+consumption+estimate' --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 Hotel Stay 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
958ms

Category:


Tags:


Related APIs