Carbon Footprint from Vehicles by Type API

Carbon Footprint from Vehicles by Type API

This calculates the footprint of a passenger vehicle based on its Type and Size, for a specific distance. This API is also used to calculate emissions related to employee business travel (including commuting) through trains, bus,es and taxis.

CarbonSutra API calculates the carbon emission footprint for your organization. Hosted at ZYLA, it can be instantly tested by yourself at no cost.

This API is used to calculate emissions when the specific make and model of vehicle is not known. It can take a generic type or size of a vehicle as its input. For example, a car could be of small size, medium, average or large. Alternatively, a car could be of mini, sports, a 4x4 or a MPV type.

The same API extends to travel by motor bikes, buses, trains and taxis. Because of its flexibility, it is used to calculate the footprints of commuting and business travel via these modes. Along with this category of vehicle and the distance travelled in either miles or kilometers, the emission is calculated.

For Scope 1, this should be used to report travel in vehicles that are owned or controlled by the reporting organization. If not owned/controlled by organization, the vehicle's emission is reported under Scope 3.

API Documentation


The Approach

We use emission factors, data, guidelines from sources like UK Government GHG factors, US Department of Energy, US Environmental Protection Agency and UK Society of Motor Manufacturers and Traders.
The API to calculate the emission is simple: it just takes the category of vehicle based on its type or size, the type of fuel that is used and the distance travelled in either miles or kilometers.
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 vehicle. Using the "include_wtt" field will add the associated upstream emission.

Ingested Data

VEHICLE_TYPE : Mandatory. The acceptable values are the following: Car-Type-Mini, Car-Type-Supermini, Car-Type-LowerMedium, Car-Type-UpperMedium, Car-Type-Executive, Car-Type-Luxury, Car-Type-Sports, Car-Type-4x4, Car-Type-MPV, Car-Size-Small, Car-Size-Medium, Car-Size-Large, Car-Size-Average, Motorbike-Size-Small, Motorbike-Size-Medium, Motorbike-Size-Large, Motorbike-Size-Average, Bus-LocalAverage, Bus-Coach, Taxi-Local, Train-National, Train-Local and Train-Tram.
DISTANCE_VALUE : Mandatory. The distance travelled by vehicle.
DISTANCE_UNIT : Mandatory. The acceptable values are "km" for kilometers and "mi" for miles. This will default to "km", if any other value is passed.
​FUEL_TYPE : Optional. There are 3 possible values here: Diesel, Petrol and Unknown. If in doubt, select the Unknown value, which is also the default.​
INCLUDE_WTT : Optional. As explained above. The default value is "Y".


Emissions from Vehicles by Type - Endpoint Features
Object Description
vehicle_type [Required] The type of vehicle for which emission is calculated. The acceptable values are: Car-Type-Mini,Car-Type-Supermini,Car-Type-LowerMedium,Car-Type-UpperMedium,Car-Type-Executive,Car-Type-Luxury,Car-Type-Sports,Car-Type-4x4,Car-Type-MPV,Car-Size-Small,Car-Size-Medium,Car-Size-Large,Car-Size-Average,Motorbike-Size-Small,Motorbike-Size-Medium,Motorbike-Size-Large,Motorbike-Size-Average,Bus-LocalAverage,Bus-Coach,Taxi-Local,Train-National,Train-Local and Train-Tram.
fuel_type [Optional] The type of fuel used in the vehicle. There are 3 possible values here: Diesel, Petrol and Unknown. If in doubt, select the Unknown value, which is also the default.
distance_value [Required] The distance travelled by vehicle. Default value is 1.
distance_unit [Required] The acceptable values are "km" for kilometers and "mi" for miles. This will default to "mi", if any other value is passed.
Test Endpoint



Emissions from Vehicles by Type - CODE SNIPPETS

curl --location --request POST '' --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 from Vehicles by Type API REST API, simply include your bearer token in the Authorization header.


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
 Response Time



Related APIs