Features · Public API

CBAM where you already work:
inside your own system, not one more tab

Dedicated API keys, machine-to-machine authentication, read endpoints for costs and registries, declaration writes that go through human supervision before confirmation. Built for teams who already have an ERP, customs software or an internal tool to connect.

🔑

API keys and M2M auth

Every key is tied to one company, with scopes and instant revocation. No shared passwords: the integration authenticates itself, tracked like any other access.

📖

Real-time reads

Declarations, CBAM cost per line, producer registry, certificate status: your system always reads the current figure, with no manual exports or end-of-day reconciliation.

🛡️

Writes with supervision

Declarations created via API land in a to-confirm state: an operator reviews them in the platform before they count toward the official cost. Automation speeds things up, it doesn't bypass control.

Actual or estimated, always labelled

Every line the API returns carries its own nature: cost from certified emissions or from a default value, so the downstream system — ERP, BI, spreadsheet — never has to guess what it's consuming.

The line-level detail exposed is the same you see in the platform: CN code, weight, emissions, ETS price applied. One number, in two places, always consistent.

EndpointMethodTypical use
/v1/bolleGETSync costs to the ERP
/v1/bollePOSTDeclaration from customs software
/v1/produttoriGETCertificate status
Calls includedin the API plan
Above thresholdusage-based add-on

Under the hood

Keys encrypted at rest, per-plan quota enforced server-side with a real-time counter; once the included threshold is passed, a billing add-on covers the extra usage without blocking the integration. Same per-company isolation (PostgreSQL Row-Level Security) as the rest of the platform — see Security.

Tell us which system you want to connect