About the API:
CarbonAPI can help you calculate your carbon footprint as a result of your emission-generating activities. The goal of our API is to contribute to the fight against climate change.
It is a simple and cost-effective way to meet your environmental reporting requirements. It can make it easier to track and measure your efforts to minimize emissions. Plus, since alternative energy sources are less expensive, your business will last longer and you can market it as eco-friendly.
When it comes to protecting the environment, calculating your impact on the planet is a great place to start. It focuses on taking decisive action to lessen the effects of climate change. It will also present you as a forward-thinking company willing to share your ideas with the rest of the world.
Calculate the CO₂e emissions of a specific flight using recognized methodologies (ICAO/myclimate) to estimate the environmental impact of air travel.
Flight clases available:
economybusinessfirstFlight Emissions - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"calculation_id":"calc_f_1309ad43","activity":"Flight from CGK to SUB","co2e_kg":176.41,"methodology_source":"ICAO/myclimate methodology"}
curl --location --request POST 'https://zylalabs.com/api/1015/carbon+footprint+tracker+api/20775/flight+emissions' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"from_airport_code": "CGK",
"to_airport_code": "SUB",
"passengers": 1,
"flight_class": "economy",
"roundtrip": false
}'
Calculate CO₂e emissions generated by freight transport using recognized methodologies (such as the GLEC framework) to assess environmental impact.
Transports Available:
truckshiprailair_freightShipping Emissions - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"calculation_id":"calc_s_c60dfbdd","activity":"Truck freight transport (100000.0 kg, 50000.0 km)","co2e_kg":310000.0,"methodology_source":"GLEC framework"}
curl --location --request POST 'https://zylalabs.com/api/1015/carbon+footprint+tracker+api/20776/shipping+emissions' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"weight_kg": 100000,
"distance_km": 50000,
"transport_method": "truck"
}'
Calculate CO₂e emissions from energy consumption in a specific country using regional emission factors to assess environmental impact.
Energy Emissions - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"calculation_id":"calc_e_16c8e575","activity":"Energy consumption in Indonesia (1000000.0 kWh)","co2e_kg":718000.0,"methodology_source":"Grid intensity data (IEA 2023)"}
curl --location --request POST 'https://zylalabs.com/api/1015/carbon+footprint+tracker+api/20777/energy+emissions' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"consumption_kwh": 1000000,
"location_country_code": "IDN"
}'
Calculate the CO₂e emissions generated by the use of a gasoline-powered vehicle using recognized DEFRA emission factors.
Vehicles available:
smallmidsizelargesuvmotorcycleFuel types available:
petroldieselelectrichybridVehicle Emissions - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"calculation_id":"calc_v_050e2874","activity":"Midsize petrol vehicle trip (50000.0 km)","co2e_kg":9450.0,"methodology_source":"DEFRA emission factors"}
curl --location --request POST 'https://zylalabs.com/api/1015/carbon+footprint+tracker+api/20778/vehicle+emissions' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"distance_km": 50000,
"vehicle_type": "midsize",
"fuel_type": "petrol"
}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Each endpoint returns the carbon emissions calculated in kilograms (kg CO2) based on the specific activity or energy source. For example, the Flight endpoint returns the CO2e from air travel, while the Car Travel endpoint provides emissions from car usage.
The key fields in the response data include "carbon," which indicates the calculated CO2 emissions, and "success," which confirms whether the calculation was successful. For instance, a response might look like `{"carbon":"2302.56 kg co2","success":true}`.
Each endpoint accepts specific parameters relevant to the activity being measured. For example, the Car Travel endpoint requires the distance driven, while the Flight endpoint needs the departure and arrival airports to calculate emissions based on distance and flight class.
The response data is structured in JSON format, with key-value pairs. The "carbon" field provides the emissions value, and the "success" field indicates the status of the request. This structure allows for easy parsing and integration into applications.
The data is derived from established emission factors based on scientific research and industry standards. For example, flight emissions are calculated using factors that consider flight distance, aircraft type, and seating class, ensuring accuracy in the results.
Typical use cases include tracking corporate carbon footprints, assessing product sustainability for marketing, and evaluating transportation options for individuals. Organizations can use this data to identify reduction opportunities and enhance sustainability reporting.
Users can customize requests by providing specific parameters relevant to their activities. For instance, when using the Fuel To Carbon endpoint, users can specify the type of fuel and the volume consumed to receive tailored emissions calculations.
If a request returns partial or empty results, users should check the input parameters for accuracy. Additionally, implementing error handling in the application can help manage unexpected responses, ensuring a smooth user experience.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). 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 paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
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.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
804ms
Service Level:
100%
Response Time:
1,077ms
Service Level:
51%
Response Time:
211ms
Service Level:
100%
Response Time:
1,247ms
Service Level:
100%
Response Time:
14,541ms
Service Level:
100%
Response Time:
665ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
177ms
Service Level:
100%
Response Time:
519ms
Service Level:
100%
Response Time:
14,043ms
Service Level:
100%
Response Time:
722ms
Service Level:
100%
Response Time:
265ms
Service Level:
100%
Response Time:
1,433ms
Service Level:
100%
Response Time:
283ms
Service Level:
100%
Response Time:
903ms
Service Level:
100%
Response Time:
1,328ms
Service Level:
100%
Response Time:
1,874ms
Service Level:
100%
Response Time:
217ms
Service Level:
100%
Response Time:
335ms
Service Level:
100%
Response Time:
218ms