Methodology is a specialty
Factors, boundaries and versions need governance your product team shouldn't have to build.
Solutions · Software & Platforms
Governed emissions, inside your product.
Give your users shipment emissions without building a methodology team. Send a calculation to the ErgOps Developer API and get back a traceable result — attributed to the right customer, with factor source and version.
For TMS, ERP, procurement and logistics platforms that want emissions as a feature.
Why platforms use ErgOps
Emissions are a feature your users now expect
Results belong to customers
Each result has to be attributed to the right customer and kept separate from others.
Integrations must be safe to retry
Timeouts happen; a retry must never create a second billable calculation.
What you integrate
A small, predictable API surface
Logistics calculation
POST a shipment and receive a calculation with activity, emissions, methodology boundary and factor lineage.
- Road, sea and air
- Only governed factor references are accepted — never raw factor values
- Unknown customer references are rejected, never auto-created
Reads
Read a calculation by its public ID, or a customer and its aggregated emissions.
- Scoped by the key's organization and environment
- Test and live data never mix
Test and live
Build against a test environment that uses the same deterministic methodology.
- Test calculations do not count toward usage
- Separate keys and webhook endpoints per environment
Documented contract
An authoritative OpenAPI specification and public guides for keys, errors, idempotency, rate limits and webhooks.
- Stable error envelope with a request ID
- Versioned /v1 contract
How it works
From test key to production
01
Create a test key
In ErgOps Embedded → Developers, with the scopes you need.
02
Map customers
Use your own customer IDs as external references.
03
Send calculations
Call the API with an Idempotency-Key per logical shipment.
04
Go live
Switch to a live key and subscribe to signed webhooks.
FAQ
Frequently asked questions
One unit is one successful live calculation attributed to one of your customers. Retries with the same Idempotency-Key, test calls, reads and webhooks do not add usage.
No. The API is server-to-server. Keep API keys in a server-side secret store and never ship them in browser code.
Read the developer quickstart at docs.ergops.com, create a test key and send your first calculation.
Keep exploring
Related pages
Add traceable emissions to your platform
Talk to us about your use case and volumes, and get started with a test key.
In the first meeting, we map your data sources, priority goals and review workflow.