A REST API over the same engine that powers EventZero: events, 16 carbon-source record types, a submit–review–approve data workflow, and audit-ready computed results — all strictly scoped to your organization.
166 operations · JSON over HTTPS · JWT bearer auth
# 1. Authenticate
curl -X POST https://api.carbon-calculator.eventzero.io/api/v2/auth/login \
-H "Content-Type: application/json" \
-d '{"email": "svc-integration@your-org.com", "password": "..."}'
# 2. Pull audit-ready carbon results for an event
curl https://api.carbon-calculator.eventzero.io/api/v2/events/665f1c2a9b1e4a0012ab34cd/results \
-H "Authorization: Bearer <accessToken>"Full lifecycle CRUD over the event portfolio, strictly scoped to your organization.
Accommodation, flights, travel, venue energy, catering, waste, freight and more — one uniform CRUD contract.
Server-calculated kgCO2e per event, built only from records your team has approved.
Invite suppliers, assign them to events, and let them submit data through the same API.
Create and update events programmatically from your registration or event-management system, so the carbon ledger always mirrors your real event portfolio — no double entry.
Venues, caterers and production partners write their own carbon-source records — flights, energy, waste, freight — directly against the events they serve, ready for your team's review.
Read computed, approval-gated carbon results per event and feed them into your data warehouse, dashboards, and ISO-aligned ESG disclosures.
Every carbon-source record moves through submit → review → approve. Suppliers and team members submit data, managers review it and leave feedback, and only approved records count toward an event's computed footprint. Your reported numbers are traceable to reviewed source data — which is exactly what auditors and ESG frameworks ask for.
How the workflow worksSubmit
A supplier or team member hands a record off for review (sets submitted).
Review
A manager reviews the record and leaves feedback for the supplier (sets reviewed).
Approve
A manager approves it — only now does it count in the event's carbon result (sets approved).
Every request is scoped to a single organization derived from the caller's identity. Cross-org access isn't filtered out — it's structurally impossible at the API layer.
Admin, manager, user, and supplier roles gate every write. Suppliers see only the events they're assigned to; approvals are manager-and-above.
Ownership, workflow flags, and timestamps are set server-side and ignored if sent by clients — the audit trail can't be forged through the API.
API access is available on partner and enterprise plans. Talk to us and we'll provision credentials for your organization.