calco2la.to

Register Login
calco2la.to
Whitepapers Connectors API Pricing Contact
Register Login
Emission calculation API

Replayable CO₂ calculation for administrative and specialist systems

The calco2la.to API is designed for system integration: transparent calculation responses, API-key based access, connector support and a roadmap towards versioned, auditable operation.

Open API docs Explore connectors Discuss a pilot

Current API state

Beta and integration-oriented

The API is currently in a beta and integration-oriented stage. Existing endpoints demonstrate airport lookup and flight emission calculation, while production hardening, versioning, rate limiting and final calculation logic remain active roadmap items.

Important: For production use, start with a pilot or organization license so API behavior, integration requirements, request volume and auditability expectations can be clarified.

Integration first

More than an isolated calculator endpoint

calco2la.to is not meant to be just another isolated calculator endpoint. The API is part of a broader integration package: connector libraries, organization-aware API-key management, replayable results and public-sector deployment support.

See integration packages
Capabilities

What the API is designed to provide

The API should support reliable use in real administrative workflows, not only ad-hoc calculations.

API-key based access

Requests are authenticated with API keys that can be managed in an organization context.

Replayable results

Responses are designed to include the relevant parameters needed to understand, document and repeat a calculation.

Time-stable factors

Calculation factors and models should be versioned and date-aware so results remain explainable over time.

Connector support

Connector libraries make it easier to integrate against a stable domain interface instead of a provider-specific API.

Current scope

Endpoint overview

The current API focus is airport-based flight emission calculation and supporting lookup endpoints.

/api/flight

Flight emission calculation

Calculates flight emissions based on departure and arrival airport data, passenger count, flight count, travel class and optional calculation parameters.

  • Supports flight-segment oriented calculation concepts.
  • Supports multiple flights in one request envelope in the API concept.
  • Returns structured JSON suitable for documentation and later verification.

/api/airports

Airport lookup and normalization

Provides airport lookup and normalization support for emission calculation requests.

  • Search and lookup by airport metadata such as IATA and ICAO codes.
  • Supports normalized airport data for calculation requests.
  • Useful for forms, validation, integrations and connector implementations.
Roadmap

Roadmap before stable production API

The API is usable as an integration direction, but the stable production offer depends on a few remaining hardening steps.

Finalize calculation logic

Replace placeholder or mock calculation paths with the final emission calculation model and factor handling.

Add rate limiting

Introduce API-key based rate limits and clear operational rules for fair use, pilots and organization licenses.

Stabilize versioning

Provide explicit API versions so integrations remain stable while calculation models and response formats evolve.

Publish OpenAPI schema

Serve a stable OpenAPI description for client generation, documentation and integration tests.

Integration model

API or connector? Usually both.

The API provides the calculation service. The connector layer makes integration safer, more flexible and less dependent on one provider-specific format.

Direct API access

Suitable for pilots, simple integrations and systems that can directly handle calco2la.to request and response formats.

Read API docs

Connector integration

Recommended when applications should remain provider-neutral, testable and easier to migrate over time.

View connectors

Organization rollout

Recommended when API keys, users, roles, sub-organizations, support and procurement requirements matter.

See packages
Evaluation

Beta use and evaluation

During the beta phase, the best next step is usually a guided evaluation rather than an unmanaged production integration.

A good pilot clarifies both API behavior and organizational fit

Use the beta phase to reduce integration and governance risk.

Good fit for a pilot

  • Testing airport-based flight emission calculation in one specialist system.
  • Comparing direct API access with connector-based integration.
  • Checking whether replayability and documentation meet administrative requirements.
  • Estimating request volume and API-key management needs.

Not yet a final production promise

  • Final rate limiting and SLA rules still need to be agreed per package.
  • Stable API versioning and OpenAPI publication are roadmap items.
  • The real emission calculation logic still needs to be finalized before full launch.
  • Framework-level usage should be planned contractually.
FAQ

Frequently asked questions

Short answers for teams evaluating API integration.

Yes, for evaluation and pilot scenarios. For regular production operation, clarify API versioning, request volume, support expectations and integration architecture first.

Not always. Direct API access may be enough for simple integrations. The connector approach is recommended when provider neutrality, migration paths, testing and long-term governance matter.

API keys are intended to be organization-bound, with management through the calco2la.to dashboard and support for ownership, revocation, expiration and usage tracking.

The current focus is airport-based flight emission calculation. The architecture is intended to grow towards additional domains and provider capabilities over time.

Planning an API integration?

Tell us which system you want to connect, whether you need direct API access or connector-based integration, and what governance or auditability requirements apply.

Discuss API pilot