API to Get the Queensland Electricity Price

You need a reliable way to pull the latest Queensland spot electricity price into a finance workflow for P&L attribution, hedging, or exposure dashboards. By the end of this guide you will query the Energy API for the Queensland Electricity symbol, parse the result, understand units and base currency handling, and be ready to ship this into a pricing or risk pipeline.

What you will fetch: Queensland Electricity (Finance)

This guide focuses on the Energy API symbol for Queensland’s wholesale spot electricity price, intended for finance use cases such as valuation inputs, settlements, or hedging analytics. Key facts you will use in code:

Illustration: API to Get the Queensland Electricity Price

Symbol name: Queensland Electricity
Symbol code: AEMO_QLD1_SPOT
Unit: AUD/MWh
Authentication: api_key query parameter (value: YOUR_API_KEY)
Endpoint: GET /api/v1/latest?symbols=
Fields to read: rates.AEMO_QLD1_SPOT, dates.AEMO_QLD1_SPOT, currencies.AEMO_QLD1_SPOT
Base currency: may be MIXED at the response level; use currencies.* for symbol-level currency
Starter plan: $19.99/mo, 7-day trial / 50 calls

Documentation and account creation are here: Documentation and Register.

First request: latest Queensland Electricity price

Make a GET request to retrieve the latest value for AEMO_QLD1_SPOT. Authentication is a simple api_key query parameter. The API returns a compact JSON with symbol-scoped rates, dates, and currencies.

cURL (copy-paste)

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

Official sample blocks

The following official cURL and JSON samples must be preserved as-is. They demonstrate the request format and response schema. Your finance code for Queensland will use the same schema fields (rates, dates, currencies) keyed by AEMO_QLD1_SPOT.

Official cURL sample

Official JSON sample

{
    "success": true,
    "date": "2026-11-06",
    "base": "EUR",
    "rates": {
        "OMIE_ES_DA": 245.6264
    },
    "dates": {
        "OMIE_ES_DA": "2026-11-06"
    },
    "currencies": {
        "OMIE_ES_DA": "EUR"
    },
    "base_filter_note": null,
    "missing_symbols": null
}

Live response example for Queensland Electricity

Below is a real response example for the Queensland Electricity symbol. Use this to validate your parsing logic and unit/currency handling in finance code. Values are specific to the symbol AEMO_QLD1_SPOT and use AUD as the currency.

What to read in finance code:

rates.AEMO_QLD1_SPOT: the latest numerical price (57.7012)
dates.AEMO_QLD1_SPOT: the effective market date for that price (2026-11-05)
currencies.AEMO_QLD1_SPOT: the currency for this symbol (AUD)
Unit reminder: AUD/MWh (keep this explicit in downstream calculations)

Python example: fetch and map into a finance pipeline

This snippet requests the latest price for AEMO_QLD1_SPOT, checks success, and extracts a finance-friendly structure including value, unit, currency, and effective date. It is minimal on purpose so you can embed it into pricing or risk code quickly.

import requests

API_URL = "https://energy-api.com/api/v1/latest"
API_KEY = "YOUR_API_KEY"
SYMBOL = "AEMO_QLD1_SPOT"

params = {
"symbols": SYMBOL,
"api_key": API_KEY
}

resp = requests.get(API_URL, params=params, timeout=10)
resp.raise_for_status()
data = resp.json()

if not data.get("success"):
raise RuntimeError("Energy API call unsuccessful")

price = data["rates"][SYMBOL]
price_date = data["dates"][SYMBOL]
currency = data["currencies"][SYMBOL]

# Finance-normalized record
record = {
"symbol": SYMBOL,
"value": float(price), # 57.7012 in the live example
"unit": "AUD/MWh", # from catalog facts
"currency": currency, # 'AUD'
"effective_date": price_date # 'YYYY-MM-DD'
}

print(record)

Field mapping and finance integration notes

For finance integrations, treat the response as a symbol-keyed snapshot with explicit per-symbol currency and date. Do not assume a portfolio-wide base currency; read currencies.AEMO_QLD1_SPOT for monetary conversions if needed downstream.

Symbol-level value: rates.AEMO_QLD1_SPOT is your primary price input.
Symbol-level date: dates.AEMO_QLD1_SPOT is the effective date to align with valuation dates and ledgers.
Symbol-level currency: currencies.AEMO_QLD1_SPOT is the currency for valuation; do not assume base applies to each symbol.
Unit: AUD/MWh. If your models operate in AUD/kWh, divide by 1000.
Base currency: base may be MIXED. Always use currencies.* for symbol currency when computing P&L or translating to portfolio currency.

Practical considerations for finance teams

Timestamps and dates: The API provides a symbol-level date field (dates.AEMO_QLD1_SPOT). Use it as the effective market date in your valuation pipeline. If you persist historical snapshots, store both the top-level date and the symbol-level date for auditing.
Market schedules: Electricity prices update throughout the day, but this endpoint returns a single latest value. If you need intraday granularity or history, design your cache/ETL to snapshot the latest regularly alongside the symbol date. Avoid assuming equities-style “market hours.”
Caching: For dashboards, cache for several minutes to reduce call volume. For trade booking and end-of-day valuation, fetch fresh data close to your valuation timestamp to avoid staleness.
Error handling: Check success boolean, and handle missing_symbols if present. On network failure, fall back to last known good value with a clear stale flag in UI/reporting.
Currency conversion: If your portfolio base is not AUD, convert after reading currencies.AEMO_QLD1_SPOT. Keep raw AUD/MWh alongside converted values for audit trails.
Do not pass base=USD when you also need symbols like TTF_GAS or EUA_CO2 in the same call, as their currencies differ; read currencies.* per symbol and convert in your finance layer.

PHP example: quick fetch for server-side valuation

Use this if your finance stack runs on PHP. It mirrors the Python mapping.

<?php
$apiUrl = "https://energy-api.com/api/v1/latest";
$params = [
"symbols" => "AEMO_QLD1_SPOT",
"api_key" => "YOUR_API_KEY"
];

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $apiUrl . "?" . http_build_query($params));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);

if ($response === false) {
throw new Exception("cURL error: " . curl_error($ch));
}
curl_close($ch);

$data = json_decode($response, true);
if (!$data || !($data["success"] ?? false)) {
throw new Exception("Energy API call unsuccessful");
}

$symbol = "AEMO_QLD1_SPOT";
$record = [
"symbol" => $symbol,
"value" => (float)$data["rates"][$symbol],
"unit" => "AUD/MWh",
"currency" => $data["currencies"][$symbol],
"effective_date" => $data["dates"][$symbol]
];

print_r($record);
?>

Validation checklist for finance deployment

Confirm symbol code: AEMO_QLD1_SPOT is in your config/allowlist.
Persist value, currency, unit, effective date, and the raw JSON for audit.
Log the api_key owner and request timestamps to trace source-of-truth in valuations.
Set timeouts and retries: 10s timeout, one retry with jitter is reasonable for interactive workflows.
Cache policy: define TTL by business need (e.g., 5–15 minutes for dashboards; near-real-time for trade booking).

FAQ

Q: What is the unit and currency for Queensland Electricity?
A: Unit is AUD/MWh. The currency field for AEMO_QLD1_SPOT is AUD; read currencies.AEMO_QLD1_SPOT in the response.

Q: Which fields should I use for valuation date alignment?
A: Use dates.AEMO_QLD1_SPOT as the effective market date for the price you ingest.

Q: Can I request multiple symbols in one call?
A: Yes, pass a comma-separated list to symbols. When mixing symbols, do not rely on the top-level base for valuation; read currencies.* for each symbol.

Q: How do I authenticate?
A: Provide your key via the api_key query parameter. Example: api_key=YOUR_API_KEY.

Q: Is there a trial for testing my finance pipeline?
A: The starter plan is $19.99/month and includes a 7-day trial with 50 calls.

Ready to wire the Queensland Electricity price into your finance stack? Create an account and get your key here: Register. For endpoint details and schema references, see the Documentation.