Carbon Interface

About Carbon Interface

Carbon Interface provides two REST APIs for generating carbon emissions estimates: the Estimates API and the Carbon Ledger API. The Estimates API calculates CO2e emissions from flights, vehicles, shipping, electricity consumption, and fuel combustion, using JSON payloads and standard HTTP requests. The Carbon Ledger API generates emissions estimates from credit card and debit transactions; it is currently in beta, with registration available for stubbed estimates and production access requiring direct contact with the provider.

Authentication uses an API key passed as a bearer token in the request header. The API returns standard HTTP status codes and descriptive JSON error messages. Estimates are calculated using emissions estimation methodologies documented separately by the provider.

The Electricity endpoint accepts consumption values in megawatt-hours or kilowatt-hours along with a country code, returning emissions in grams, pounds, kilograms, and tonnes; it supports North American and European countries and sub-regions, with optional state-level detail for more accurate results in the US and Canada. The Flight endpoint accepts passenger count, flight legs with departure and destination airport codes, and cabin class, returning distance and emissions data. The Shipping endpoint accepts weight, distance, and transport method (ship, train, truck, or plane) to compute emissions for a shipment. The service is intended for developers integrating carbon emissions calculations into applications.

Key features

• Estimates API for CO2e emissions from electricity, flights, shipping, vehicles, and fuel combustion
• REST API with JSON request/response payloads
• Carbon Ledger API for estimating emissions from credit card and debit transactions (beta)
• Electricity emissions estimates with country and US/Canada state-level granularity
• Flight emissions estimates supporting multi-leg and round-trip itineraries
• Postman collection for testing endpoints before integration

Frequently asked questions