CarbonSutra Carbon Emissions API
API platform for carbon-emission estimation and consolidation.
CarbonSutra API
CarbonSutra provides developer APIs for estimating and consolidating carbon dioxide equivalent (CO₂e) emissions across business activities.
The platform is designed for applications supporting carbon accounting, ESG and sustainability reporting, compliance workflows, environmental analysis, mitigation, offsetting, and decarbonization programs.
Core capabilities
- Business travel — Flight emissions using airports, cabin class, passengers, round-trip travel, radiative forcing, and Well-to-Tank (WTT) options.
- Accommodation — Hotel emissions using country, city, hotel rating, nights, and rooms.
- Transportation — Vehicle emissions by vehicle type or specific make and model.
- Electricity — Electricity-consumption emissions by country and consumption unit.
- Fuel — Emissions from gas, liquid, and solid fuel consumption.
- Freight — Road, rail, air, sea, and intermodal shipment estimates.
- eCommerce — Shipment estimates using origin/destination countries and postal codes.
- Developer utilities — Vehicle catalogs and airport search/distance utilities.
- Emission clusters — Optional server-side grouping and retrieval of calculated emissions.
Authentication
Protected endpoints use a CarbonSutra API key as a Bearer token:
Code
Some utility endpoints are public and do not require authentication.
Emission units
Calculation results may include:
co2e_gm— grams of CO₂eco2e_kg— kilograms of CO₂eco2e_mt— metric tonnes of CO₂eco2e_lb— pounds of CO₂e
API conventions
All endpoints are versioned under /api/v1/. The supplied API collection exposes calculation inputs as query parameters, including for POST operations.
A cluster_name can be supplied when an authenticated calculation should be associated with an emission cluster.
Specification scope
This specification reflects the supplied CarbonSutra Postman collection. Where the collection did not define a complete response structure, this document uses a generic JSON response rather than inventing unsupported fields.

