Historical Portugal OMIE Day-Ahead Prices

You need reliable historical Portugal OMIE Day-Ahead power prices to drive finance workflows like PPA indexation, hedging back-tests, risk factor calibration, and settlement checks. By the end of this guide you will query, parse, and validate the Portugal OMIE Day-Ahead timeseries (symbol OMIE_PT_DA) from Energy API, and wire it into your pricing and risk pipelines.

What you are integrating and why it matters for finance

This guide focuses on the Portugal OMIE Day-Ahead price series, symbol OMIE_PT_DA, in EUR/MWh. These day-ahead auction outcomes are a primary input to:

• Risk modeling: build return distributions, stress windows, and historical VaR inputs for Iberian power desks.
• Back-testing: evaluate strategy performance and hedges against historical OMIE_PT_DA paths.
• Settlement and accruals: reconcile invoices and index-linked PPAs using transparent day-ahead benchmarks.
• Scenario analysis: feed price trajectories into cash flow models to test contract optionality and collateral triggers.

Portugal OMIE Day-Ahead: symbol and units

Energy API provides a cataloged symbol for Portugal day-ahead power:

• Symbol name: Portugal OMIE Day-Ahead
• Symbol code: OMIE_PT_DA
• Unit: EUR/MWh
• Auth: api_key query parameter (use YOUR_API_KEY)

The OMIE_PT_DA series represents day-ahead market outcomes. All examples in this post are specific to finance workflows that require consistent units (EUR/MWh) and robust handling of missing or auction-holiday days.

Endpoint and authentication

You will call a single endpoint to retrieve historical data over a date window:

• HTTP method: GET
• Endpoint: https://energy-api.com/api/v1/timeseries
• Parameters: start, end, symbols, api_key
• Symbols: comma-separated, e.g., OMIE_PT_DA
• Auth: api_key is passed as a query parameter

Do not add unrelated parameters. If you also need TTF_GAS or EUA_CO2 for cross-factor analysis, do not pass base=USD at the same time; keep the default base and read each symbol’s currency field explicitly.

Quick start with curl

Use this copy-pasteable curl to fetch a historical window. It returns rates keyed by symbol and includes metadata for date and currency. Keep YOUR_API_KEY as-is when testing locally until you replace it with your actual key.

curl -G "https://energy-api.com/api/v1/timeseries" --data-urlencode "start=2026-01-01" --data-urlencode "end=2026-03-31" --data-urlencode "symbols=OMIE_PT_DA" --data-urlencode "api_key=YOUR_API_KEY"

JSON field guide

You will read three fields for finance-grade processing:

• rates.OMIE_PT_DA: numeric price in EUR/MWh
• dates.OMIE_PT_DA: ISO date of the observation
• currencies.OMIE_PT_DA: currency code (EUR)

The following are complete JSON examples you can use to verify your parser. Read the notes carefully to avoid off-by-one-day or currency mismatches.

Official sample JSON (from live source)

This sample is provided as-is from the official source. It demonstrates the response shape but references a different Iberian symbol (OMIE_ES_DA). Your integration logic remains identical. Use the Portugal symbol OMIE_PT_DA in production.

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

Real API response for Portugal OMIE Day-Ahead (use these exact values)

This is the real response block you should mirror for tests against the Portugal symbol OMIE_PT_DA.

{"success":true,"date":"2026-10-14","base":"EUR","rates":{"OMIE_PT_DA":186.4441},"dates":{"OMIE_PT_DA":"2026-10-14"},"currencies":{"OMIE_PT_DA":"EUR"},"base_filter_note":null}

Field-access validation example (Portugal)

Use the same response again to confirm your extraction logic is deterministic and idempotent in test suites.

{"success":true,"date":"2026-10-14","base":"EUR","rates":{"OMIE_PT_DA":186.4441},"dates":{"OMIE_PT_DA":"2026-10-14"},"currencies":{"OMIE_PT_DA":"EUR"},"base_filter_note":null}

How to parse Portugal OMIE Day-Ahead in Python

This Python example queries the same endpoint and reads the three fields you care about for finance-grade ingestion. It normalizes output into a row with date, price, and currency for downstream calculations.

import requests
from datetime import date

BASE_URL = "https://energy-api.com/api/v1/timeseries"

params = {
"start": "2026-01-01",
"end": "2026-03-31",
"symbols": "OMIE_PT_DA",
"api_key": "YOUR_API_KEY"
}

resp = requests.get(BASE_URL, params=params, timeout=30)
resp.raise_for_status()
data = resp.json()

# Validate top-level success and base
if not data.get("success", False):
raise RuntimeError("API returned success=false")
if data.get("base") != "EUR":
# For finance workflows that need consistent currency constraints
raise ValueError(f"Unexpected base: {data.get('base')}")

symbol = "OMIE_PT_DA"

# Extract core fields
price = data.get("rates", {}).get(symbol)
obs_date = data.get("dates", {}).get(symbol)
currency = data.get("currencies", {}).get(symbol)

# Hard validation for production
if price is None or obs_date is None or currency is None:
raise KeyError("Missing one of rates/dates/currencies for OMIE_PT_DA")

# Normalize to a finance-friendly record
record = {
"symbol": symbol,
"observation_date": obs_date, # ISO 8601 date
"price_eur_per_mwh": float(price),
"currency": currency
}

print(record)

How to parse in JavaScript (Node.js) if you prefer

Same endpoint, same fields. This snippet uses fetch and produces an object ready for pricing and risk engines.

import fetch from "node-fetch";

const BASE_URL = "https://energy-api.com/api/v1/timeseries";

async function fetchPortugalOMIEDayAhead() {
const url = new URL(BASE_URL);
url.searchParams.set("start", "2026-01-01");
url.searchParams.set("end", "2026-03-31");
url.searchParams.set("symbols", "OMIE_PT_DA");
url.searchParams.set("api_key", "YOUR_API_KEY");

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

if (data.success !== true) {
throw new Error("API returned success=false");
}

const symbol = "OMIE_PT_DA";
const price = data?.rates?.[symbol];
const obsDate = data?.dates?.[symbol];
const currency = data?.currencies?.[symbol];

if (price == null || obsDate == null || currency == null) {
throw new Error("Missing rates/dates/currencies for OMIE_PT_DA");
}

return {
symbol,
observation_date: obsDate,
price_eur_per_mwh: Number(price),
currency
};
}

fetchPortugalOMIEDayAhead()
.then((rec) => console.log(rec))
.catch((err) => console.error(err));

What the fields mean for your finance stack

Interpret each field with a finance lens:

• date: the API processing date. Use dates.OMIE_PT_DA for the actual observation date to avoid ambiguity.
• rates.OMIE_PT_DA: the price value. Store it as a floating point or decimal with adequate precision; it is EUR/MWh.
• currencies.OMIE_PT_DA: currency code. Keep it to enforce valuation constraints in multi-factor models.
• base: the API’s base currency. Leave it at EUR when working with OMIE_PT_DA. Do not coerce to another base alongside TTF_GAS or EUA_CO2.

Operational details that save time

• Timezones and day alignment: OMIE day-ahead prices correspond to the auction’s next-day delivery. Use dates.OMIE_PT_DA to align to the intended value date in your ledger or PnL timeseries.
• Units: All values are in EUR/MWh. Maintain unit fidelity through your pipeline. If you must convert to EUR/kWh, apply a strict 0.001 factor only downstream.
• Non-trading/holiday behavior: If the OMIE market doesn’t hold a session that results in a new value for a given date, expect no new observation for that delivery date. Your ingestion should handle sparse sequences without forward-filling unless your finance policy explicitly requires it.
• Caching: For back-testing or risk replays, cache immutable historical windows locally. In live recalcs, set cache eviction based on your revaluation cadence; day-ahead benchmarks typically need one refresh per new auction cycle.
• Integrity checks: Enforce monotonically progressing observation dates, reject nulls, and validate currency=EUR. Flag significant outliers using rolling z-scores before they reach pricing engines.

Reading data safely in production

Two practical safeguards are worth the few lines of code they take:

• Schema guardrails: Assert that rates, dates, and currencies contain the requested symbol key OMIE_PT_DA before processing. Crash early in staging, not in settlement windows.
• Date reconciliation: Always prefer dates.OMIE_PT_DA for indexing your warehouse table. The top-level date is the response date, not necessarily the observation’s value date.

A third JSON echo to lock down your tests

Many finance teams keep a canonical fixture to validate parsers. Keep this exact response as a fixture for CI and golden-file tests.

{"success":true,"date":"2026-10-14","base":"EUR","rates":{"OMIE_PT_DA":186.4441},"dates":{"OMIE_PT_DA":"2026-10-14"},"currencies":{"OMIE_PT_DA":"EUR"},"base_filter_note":null}

Common pitfalls to avoid

• Mixing bases with cross-commodities: Do not pass base=USD when you also need TTF_GAS or EUA_CO2 in the same pipeline. Read each symbol’s currency explicitly and convert in your valuation layer if required.
• Assuming hourly granularity: This symbol represents day-ahead outcomes. If you need hourly shapes, source them separately and maintain a clear distinction in your models.
• Silent forward-fills: Finance controls often require raw index values. If you apply forward-fills, tag them explicitly and keep the original series untouched for audit.
• Environment drift: Keep YOUR_API_KEY out of source control. Parameterize start, end, and symbols in your CI/CD and IaC templates.
• MCP host or alternate endpoints: There is no MCP host for this integration. Use the documented endpoint only.

Plan notes and request budgeting

Starter is $19.99/mo with a 7-day trial and 50 calls. Budget your trial usage around the number of back-test windows you need to pull. For example, back-filling four quarterly windows plus a current snapshot fits well within the allowance if you batch symbols logically.

End-to-end workflow checklist

• Choose the symbol OMIE_PT_DA and fix units as EUR/MWh.
• Call GET /api/v1/timeseries with start, end, symbols, and api_key=YOUR_API_KEY.
• Parse rates.OMIE_PT_DA, dates.OMIE_PT_DA, currencies.OMIE_PT_DA.
• Index storage tables by dates.OMIE_PT_DA; store currency alongside numeric price.
• Run integrity checks: non-null, currency=EUR, date continuity (no duplicates).
• Wire to finance models: PnL, risk factors, accruals, and settlements.

FAQ

Q: Which symbol should I request for Portugal day-ahead prices?
A: Use OMIE_PT_DA. It returns values in EUR/MWh with dates and currency metadata.

Q: How do I authenticate?
A: Pass your API key as a query parameter: api_key=YOUR_API_KEY.

Q: What fields do I need for a robust finance ingestion?
A: Read rates.OMIE_PT_DA for the price, dates.OMIE_PT_DA for the observation date, and currencies.OMIE_PT_DA to enforce EUR in your valuation layer.

Q: Can I change the base currency?
A: Avoid changing base when you also need TTF_GAS or EUA_CO2. Keep the default base and convert in your pricing layer if necessary.

Q: How should I handle days with no new auction value?
A: Do not forward-fill unless your policy demands it. Store only actual observations and apply any fills in a separate, annotated view.

Ready to integrate OMIE_PT_DA into your finance stack? Create an account and start your 7-day trial with 50 calls: Register. For parameter details and edge cases, see the Documentation and ship your ingestion today.