Name: EcoFreight Freight Emissions API
Brand: EcoFreight
Availability: InStock

Question 1

How do I get started with the EcoFreight API?

Accepted Answer

Create a free account from the dashboard to receive an API key. The REST API documentation is at /docs (powered by an OpenAPI 3.1 spec at /openapi.json). The first /calculate request is one curl call away — see the example on the homepage.

Question 2

What transport modes does the API support?

Accepted Answer

Road (heavy 16t+, medium 7.5-16t, light <7.5t, electric), sea (container 3000-8000 TEU, 8000+ TEU, bulk carriers, tankers), rail (diesel and electric freight), and air (dedicated cargo and belly cargo). Each mode uses GLEC Framework v3.2 default emission factors aligned with ISO 14083:2023.

Question 3

How accurate are the CO₂ emission calculations?

Accepted Answer

We use GLEC Framework v3.2 default factors at ISO 14083 Tier 1 (modelled defaults). Accuracy depends on input data quality: if you provide measured fuel burn for a specific voyage we will return a Tier 3 (primary) result; with only origin, destination, mode and cargo weight, we return a Tier 1 default. Each response includes a methodology field so you can see which tier was used.

Question 4

What are the API rate limits?

Accepted Answer

The Free tier includes 1,000 requests per month with no credit card required. Growth is $19 per month (or $159 per year) for 50,000 requests. Enterprise is custom — email sales@ecofreight.co with your expected monthly volume.

Question 5

Do you provide SDKs?

Accepted Answer

Not yet. The REST API is documented at /docs and any HTTP client (curl, fetch, requests, axios, OkHttp) works. Python and Node SDKs are on the roadmap — check /roadmap for status.

Question 6

How do I handle API errors and edge cases?

Accepted Answer

The API returns standard HTTP status codes: 200 on success, 400 for invalid input (with a field-level errors array in the body), 401 for missing or invalid API key, 429 for rate-limit exceeded, 500 for server errors. Every error response includes a request_id you can quote when contacting support.

Question 7

Can I get historical data for my shipments?

Accepted Answer

The calculation response includes a calculation_id you can store. We do not persist your shipment payloads beyond 30 days for privacy reasons. If you need long-term storage of computed results, store the response in your own system using calculation_id as a stable reference.

Question 8

What data do I need to provide for accurate calculations?

Accepted Answer

Minimum: origin, destination, transport mode, and cargo weight (in kg). Recommended: vessel/vehicle type and cargo category — these refine the emission factor used. Optional but powerful: primary fuel-burn data, which moves the result from ISO 14083 Tier 1 to Tier 3.

Question 9

How do you ensure data privacy and security?

Accepted Answer

All API traffic uses TLS 1.3. Shipment payloads are processed in memory and deleted within 30 days. We do not sell or share customer data. See the Privacy Policy at /privacy for full details.

Question 10

Is the methodology peer-reviewed?

Accepted Answer

We follow the GLEC Framework v3.2 (published by Smart Freight Centre, the industry standard maintainer) and ISO 14083:2023. Both are publicly available — links and full data quality tier breakdowns are on the /methodology page.

How can we help you?

Frequently asked questions