EUA CO2 Price API

You need to fetch the latest EUA CO2 price for finance workflows like daily valuation, carbon exposure tracking, and backtesting. By the end of this guide, you will query the Energy API for the EUA CO2 symbol, parse the response fields you actually need, and integrate those values safely into pricing, risk, and reporting jobs.

What the latest-price endpoint returns for EUA CO2

This section compiles the essentials you’ll use in production so you can wire the call once and re-use it across services.

• Endpoint and method: GET https://energy-api.com/api/v1/latest
• Query parameters you must provide:
  • symbols=EUA_CO2
  • api_key=YOUR_API_KEY
• Authentication: api_key query parameter (no headers required)
• Response fields to read:
  • rates.EUA_CO2 — latest price
  • dates.EUA_CO2 — price date
  • currencies.EUA_CO2 — currency code for the symbol
  • base — may be EUR or MIXED based on symbol set; do not force USD for EUA_CO2
• Units: EUR/MT for EUA CO2
• Plan notes: Starter $19.99/mo, 7-day trial with 50 calls
• Host: No MCP; use the public base URL above

ORIGIN CATALOG FACTS

• Symbol name: EUA CO2
• Symbol code: EUA_CO2
• Unit: EUR/MT
• Auth: api_key query parameter. Placeholder YOUR_API_KEY only.
• Do not pass base=USD when you also need TTF_GAS or EUA_CO2.
• No MCP host. Starter $19.99/mo, trial 7 days / 50 calls.
• curl: curl -G "https://energy-api.com/api/v1/latest" --data-urlencode "symbols=EUA_CO2" --data-urlencode "api_key=YOUR_API_KEY"
• Read rates.EUA_CO2, dates.EUA_CO2, currencies.EUA_CO2. base may be MIXED.

Quickstart: get the latest EUA CO2 price with curl

Copy and run this with your api_key. It returns a compact payload you can parse in a shell, cron job, CI, or serverless function.

curl -G "https://energy-api.com/api/v1/latest" --data-urlencode "symbols=EUA_CO2" --data-urlencode "api_key=YOUR_API_KEY"

For development, keep it simple: pass only the required parameters and avoid adding a base override when requesting EUA_CO2.

REAL API RESPONSE for EUA_CO2

Below is an official EUA CO2 example you can use for local tests and schema validation. Use these exact values when writing fixtures.

{"success":true,"date":"2026-10-01","base":"EUR","rates":{"EUA_CO2":78.017},"dates":{"EUA_CO2":"2026-10-01"},"currencies":{"EUA_CO2":"EUR"},"base_filter_note":null}

What you will actually use:

• rates.EUA_CO2: 78.017 — latest EUA CO2 price
• dates.EUA_CO2: 2026-10-01 — price date for EUA CO2
• currencies.EUA_CO2: EUR — currency for the symbol
• base: EUR — overall base for the call; do not coerce to USD for EUA_CO2

Alternate live-sample payload (schema-identical)

This official sample from the live feed shows the same structure you will parse. It is not EUA_CO2, but the schema is identical and safe to use for integration tests.

{
"success": true,
"date": "2026-10-20",
"base": "EUR",
"rates": {
"OMIE_ES_DA": 195.5215
},
"dates": {
"OMIE_ES_DA": "2026-10-20"
},
"currencies": {
"OMIE_ES_DA": "EUR"
},
"base_filter_note": null
}

When substituting EUA_CO2 in symbols, expect the same keys under rates, dates, and currencies, but with EUA_CO2 as the object key.

Parse EUA CO2 in code (JavaScript)

The following example calls the latest endpoint for EUA_CO2, validates the response, and exposes typed values you can feed into valuation or risk steps. It assumes no base override is sent for EUA_CO2.

async function fetchLatestEuaCo2(apiKey) {
const url = new URL("https://energy-api.com/api/v1/latest");
url.searchParams.set("symbols", "EUA_CO2");
url.searchParams.set("api_key", apiKey);

const res = await fetch(url.toString(), { method: "GET" });
if (!res.ok) {
throw new Error("HTTP " + res.status + " fetching EUA_CO2");
}
const data = await res.json();

// Basic schema checks
if (!data || data.success !== true) {
throw new Error("API did not return success=true");
}
if (!data.rates || typeof data.rates.EUA_CO2 !== "number") {
throw new Error("Missing rates.EUA_CO2");
}
if (!data.dates || typeof data.dates.EUA_CO2 !== "string") {
throw new Error("Missing dates.EUA_CO2");
}
if (!data.currencies || typeof data.currencies.EUA_CO2 !== "string") {
throw new Error("Missing currencies.EUA_CO2");
}

// Extract stable fields you will store downstream
const latest = {
symbol: "EUA_CO2",
price: data.rates.EUA_CO2, // number
priceDate: data.dates.EUA_CO2, // ISO date string
currency: data.currencies.EUA_CO2, // e.g., "EUR"
base: data.base || null, // "EUR" or "MIXED" depending on query
asOfDate: data.date || null // top-level date from the feed
};

// Example: validate base semantics for EUA_CO2
// For EUA_CO2 specifically, do not coerce to USD or pass base=USD.
if (latest.base === "MIXED") {
// This state appears when mixing symbols with different currencies.
// For single-symbol EUA_CO2 calls, base is generally "EUR".
}

return latest;
}

// Example usage:
fetchLatestEuaCo2("YOUR_API_KEY")
.then((x) => {
console.log("EUA_CO2", x.price, x.currency, "as of", x.priceDate);
})
.catch((err) => {
console.error(err);
});

Store price as a decimal number alongside its currency (EUR) and price date for auditability. If you fan out to multiple symbols later, be aware that base can change to MIXED; in that case, your valuation layer must use the per-symbol currency field rather than a global base assumption.

Copy-paste payloads for fixtures and CI

Use these complete JSON blocks unchanged in unit tests and contract checks. They reflect the exact schema and values used above.

Fixture A — EUA_CO2 single-symbol response

{"success":true,"date":"2026-10-01","base":"EUR","rates":{"EUA_CO2":78.017},"dates":{"EUA_CO2":"2026-10-01"},"currencies":{"EUA_CO2":"EUR"},"base_filter_note":null}

Fixture B — Schema parity check from live sample

{
"success": true,
"date": "2026-10-20",
"base": "EUR",
"rates": {
"OMIE_ES_DA": 195.5215
},
"dates": {
"OMIE_ES_DA": "2026-10-20"
},
"currencies": {
"OMIE_ES_DA": "EUR"
},
"base_filter_note": null
}

Finance integration notes and edge cases

Units and currency:

• Symbol EUA_CO2 is quoted in EUR per metric ton (EUR/MT). Do not assume USD. Always store currencies.EUA_CO2 alongside the numeric price.
• Do not pass base=USD when requesting EUA_CO2. The API may set base to EUR or MIXED depending on the symbols set. For single-symbol EUA_CO2 queries, base commonly returns EUR.

Timestamps and dates:

• Use dates.EUA_CO2 as the authoritative price date for the symbol. The top-level date reflects the feed date; they typically match for a single-symbol call.
• Normalize to UTC in downstream systems if you enrich with other data sources. The API returns ISO date strings without explicit time components in the samples.

Caching:

• Daily-priced symbols benefit from a per-symbol cache keyed by dates.EUA_CO2. When the date does not change, you can safely reuse the prior value for end-of-day processes.
• When you mix symbols with different posting schedules, do not share caches across symbols. The base may become MIXED and per-symbol dates differ.

Non-trading days and refresh cadence:

• Expect stable daily values across weekends or holidays depending on market calendars. Your job code should tolerate an unchanged dates.EUA_CO2 while still recording the run date for audit.
• If your system requires intraday refresh, re-call on your schedule and rely on dates.EUA_CO2 to detect whether a price roll occurred.

Error handling:

• Check success === true before reading fields.
• Guard for missing rates.EUA_CO2 or unexpected types, and fall back to the last known good value if your Finance system supports that pattern.

From sandbox to production

Environment strategy:

• Use a dedicated trial key in development. The trial allows 7 days and 50 calls, which is sufficient for wiring CI checks and a few manual runs.
• In CI, validate that your parser reads rates.EUA_CO2, dates.EUA_CO2, currencies.EUA_CO2, and base. Fail builds if any key is missing to avoid silent regressions.

Secret management and transport:

• Store YOUR_API_KEY in your secret manager. Do not hardcode it in source control.
• Calls are HTTPS GET with query parameters. Ensure logs do not print full URLs in production; scrub the api_key when logging.

Data modeling:

• Persist a normalized record: symbol=EUA_CO2, price (decimal), currency=EUR, price_date (date), base (string), as_of_date (date), source=Energy API.
• For cross-currency P&L, convert downstream using your treasury FX stack instead of forcing a base on the Energy API call for EUA_CO2.

Troubleshooting checklist

• Received MIXED base when expecting EUR: Verify you only requested symbols=EUA_CO2. Mixing symbols can change base to MIXED.
• Price unchanged day-over-day: Confirm your calendar logic; EUA CO2 can have the same value across non-trading days. Rely on dates.EUA_CO2 to detect rollovers.
• HTTP 4xx with valid key: Ensure the api_key is sent as a query parameter and is not URL-encoded incorrectly (most HTTP clients handle encoding automatically).
• Parsing errors: Confirm you are reading nested fields under rates, dates, currencies with the EUA_CO2 key, not top-level fields.

FAQ

How do I request only EUA CO2 without currency conversion?
Call GET https://energy-api.com/api/v1/latest with symbols=EUA_CO2 and api_key=YOUR_API_KEY, and do not pass a base override. Read the per-symbol currency in currencies.EUA_CO2.

Which fields should my Finance system store?
Store rates.EUA_CO2 (numeric price), dates.EUA_CO2 (price date), currencies.EUA_CO2 (currency code), base (EUR or MIXED), and the top-level date for reconciliation.

What unit is the EUA CO2 price in?
EUR per metric ton (EUR/MT). Keep units attached in your schema to avoid misinterpretation during analytics and reporting.

Can I batch EUA CO2 with other symbols?
Yes, but the base may become MIXED. Always rely on the per-symbol currency and date fields when batching.

Is there a free way to prototype?
Yes. The Starter plan has a 7-day trial with 50 calls, which is enough to wire the endpoint, write tests, and validate your Finance pipelines.

When you are ready to ship, create your key and follow the field-level notes in the docs: Register and read the endpoint reference here: Documentation.