Slovenia has two million people and a power exchange that sets reference prices across south-east Europe. If you are building anything that touches the Balkans or the Italian border, this is the market you cannot skip.
BSP SouthPool — the South East Europe power exchange — runs the Slovenian day-ahead and intraday markets and is coupled with Italy and Austria. Its public history is thin, so for long series ENTSO-E is the practical source.
BSP SouthPool operates the Slovenian day-ahead and intraday markets, and its prices are used as a reference well beyond the Slovenian border. Slovenia sits between Italy, Austria, Croatia and Hungary, and price differences across those borders are where cross-border trading lives.
That explains an odd measurement: "bsp southpool" is searched more than the national TSO of most European countries. The people searching are not Slovenian retail customers — they are traders and developers in the surrounding markets.
Neither publisher offers a large public developer API in the style of RTE or Elexon. In practice there are three routes, and which one you pick depends on whether you need it automated.
| Route | What it gives you | Automatable |
|---|---|---|
ENTSO-E, zone 10YSI-ELES-----O | Day-ahead prices, load, generation, cross-border flows, balancing — in the same schema as every other European zone. | Yes — this is the practical route for almost everything. |
| BSP SouthPool site | Market results, volumes, coupling outcomes, published as reports and downloadable files. | Partly — files are regular but the structure is not a contract. |
| ELES | System operation data, transparency reporting, balancing. | Partly — much of it also reaches ENTSO-E. |
Slovenia is coupled to Italy, Austria, Croatia and Hungary. Price convergence with any of them tells you the interconnector is not binding; divergence tells you it is. Because Slovenia sits between the expensive Italian market and cheaper central Europe, the Italian border in particular is frequently constrained.
Slovenian generation leans on hydro, lignite and the Krško nuclear plant, which is jointly owned with Croatia and counted half to each. One unit outage moves a market this size substantially — the availability data matters more here than in a system with fifty comparable plants.
Thin markets have wider intraday spreads and thinner order books. For anyone building execution logic this cuts both ways: there is more edge in the spread, and considerably less liquidity to take it with. Assumptions carried over from Germany do not survive here.
Slovenia is usually the entry point to a wider question. The neighbouring zones follow the same pattern — a national TSO with modest public data, an exchange with published results, and ENTSO-E carrying a comparable subset for all of them:
10YHR-HEP------M, exchange CROPEX10YHU-MAVIR----U, exchange HUPX10YCS-SERBIATSOV, exchange SEEPEX10Y1001A1001A73I, the zone Slovenia trades against mostBuilding one ENTSO-E integration and switching the domain parameter gets you all of them at once, which is exactly the case where the common schema beats richer national sources.
We build market data pipelines that cover several coupled zones from one codebase — Slovenia, Croatia, Hungary, Italy North — with the cross-border logic that makes them worth having together. Talk to us.
Get in touch