ENTSOG Transparency Platform API: how to query European gas flows
Published . Every request was run against transparency.entsog.eu on 10 Nov 2026
The ENTSOG Transparency Platform API is free and needs no key: send a GET request to https://transparency.entsog.eu/api/v1/operationalData with indicator=Physical%20Flow, periodType=day, a from and to gas day and the pointDirection of each operator, point and direction you want, and it answers in JSON, or in CSV, XML or XLSX if you add the extension.
Values are in kWh/d per gas day, which runs 06:00 to 06:00 German time. A call returns 100 rows unless you set limit, and ENTSOG stops any query after 60 seconds, so ask for about a month at a time. The live table below comes from exactly these requests.
Norway's entry flows, read through the API
Voltstack's Norway gas flows page reads the entry Physical Flow of the operators that receive Norwegian gas. This table is that same read: of the two gas days before the one still running, whichever more landing points have published, the later on a tie: 16 Nov 2026, in GWh/d.
| Landing point | Country | pointDirection keys (ENTSOG) | GWh/d |
|---|---|---|---|
| Emden (EPT1) | Germany | DE-TSO-0009ITP-00080entry, DE-TSO-0005ITP-00081entry, DE-TSO-0002ITP-00105entry, NL-TSO-0001ITP-00160entry | 1,058 |
| Dornum | Germany | DE-TSO-0009ITP-00126entry | 754 |
| Dunkerque | France | FR-TSO-0003ITP-00045entry | 106 |
| Zeebrugge ZPT | Belgium | BE-TSO-0001ITP-00106entry | 481 |
| Easington | Great Britain | UK-TSO-0001ITP-00091entry | 844 |
| Total, 5 of 5 landing points (Voltstack's calculation from ENTSOG data) | 3,243 | ||
| St Fergus | Great Britain | Not counted. National Gas reports the St Fergus terminal as one figure, with UK North Sea gas in it. | |
| Nybro (Baltic Pipe) | Denmark | Not counted. Energinet's North Sea Entry also carries Danish gas from Tyra. | |
Emden is the sum of four operators' rows, and counts only on a gas day when all four have published. Each value is ENTSOG's kWh/d divided by a million. The read asks for one quarter per request, 24 requests from 1 Jan 2021, and holds 2,146 gas days from 1 Jan 2021. This is the request for the current quarter, as the module sends it:
https://transparency.entsog.eu/api/v1/operationalData?indicator=Physical%20Flow&periodType=day&timeZone=CET&from=2026-10-01&to=2026-11-17&limit=2000&pointDirection=de-tso-0009itp-00080entry,de-tso-0005itp-00081entry,de-tso-0002itp-00105entry,nl-tso-0001itp-00160entry,de-tso-0009itp-00126entry,fr-tso-0003itp-00045entry,be-tso-0001itp-00106entry,uk-tso-0001itp-00091entryOne gas day for every row and the total, never a mix of days; the gas day still running is never counted. Read through Next.js's data cache, which keeps the open quarter for up to an hour; the page re-renders every 15 minutes. The total is added up before rounding, so it can differ from the sum of the 5 rounded rows by up to 2. SOURCE: ENTSOG TP 18-11-2026 https://transparency.entsog.eu/. Totals, sums, averages, ranges and comparisons shown are Voltstack calculations from ENTSOG TP data, not ENTSOG figures, and ENTSOG does not endorse them. ENTSOG accepts no liability for data that has been altered or processed (ENTSOG TP Terms of Use, Art. 5.5).
Voltstack reads ENTSOG physical flows at the main EU import points, Norwegian, Algerian, TAP and TurkStream gas, and shows them next to EU storage, LNG send-out and power in one workspace, naming the source on each. The 14-day trial opens the workspace. The Voltstack API is in early access: keys are issued on request, not self-serve.
Start a 14-day free trialRequest early access →The button opens a 14-day free trial sign-up. Sign-up needs a work email.
The button opens the early-access request on our home page.
One base URL, an endpoint, and filters
Every call is a GET to https://transparency.entsog.eu/api/v1/ followed by an endpoint. There is no key, no token and no sign-up. Any field in the answer can be used as a filter, values are case-sensitive, and a comma separates several values for one parameter (ENTSOG TP API User Manual v3.0, 1 Oct 2025, sections 2.1 and 2.3). Flows live in operationalData; the other endpoints here tell you which keys to ask for.
| Endpoint | What it holds |
|---|---|
| /operationalData | Nominations, allocations, physical flows, capacities, GCV and more, per operator, point, direction and period. Also /operationaldatas: the manual says both return the same. |
| /interconnections | Each interconnection between an exit system and an entry system, with both operators and both point keys. Filter by fromCountryKey or toCountryKey. |
| /operatorPointDirections | Every operator, point and direction known to the platform. hasData=1 keeps those of operators that publish (manual 2.4.7). |
| /connectionPoints | The main points on ENTSOG’s map, not the operators’ sub-points: ITP-00209 answers, ITP-00080 does not. |
| /operators | Operator keys and names: NO-TSO-0001 is Gassco. |
The parameters for physical flows
| Parameter | Example | Rule |
|---|---|---|
| indicator | Physical Flow | Case-sensitive (manual 2.3, 2.4.4). Comma-separate several. "physical flow" answers 404. |
| periodType | day | day or hour (manual, Annex I). The Norwegian entry legs on this page publish daily rows. |
| from, to | 2026-11-01 | YYYY-MM-DD gas days, both included: from=2026-11-01&to=2026-11-07 returns seven daily rows per leg. |
| pointDirection | DE-TSO-0009ITP-00126entry | operatorKey, pointKey and directionKey written together; comma-separate several. |
| timeZone | CET | How date filters are read (manual 2.4.2). Daily rows came back the same under CET, WET, UCT or none. |
| limit | -1 | 100 rows when left out; -1 for every row (manual 2.4.3). See section 05 before you page. |
| includeExemptions | 0 | 1 adds rows marked not applicable, with an empty value (manual 2.4.8). |
In the answer, periodFrom and periodTo bound each row; as filters they are written from and to (manual 2.1). value is in the row's unit, kWh/d for daily physical flow, so divide by a million for GWh/d. flowStatus reads Provisional or Confirmed, and lastUpdateDateTime says when the operator last touched the row.
Observed on transparency.entsog.eu on 10 Nov 2026. SOURCE: ENTSOG TP 10-11-2026 https://transparency.entsog.eu/.
pointDirection: operator, point, direction
A pointDirection is an operatorKey, a pointKey and a directionKey written together, so OGE's entry at Dornum is DE-TSO-0009ITP-00126entry. ENTSOG calls these operator point directions and lists them all at /operatorPointDirections (manual 2.4.7). ENTSOG writes them in capitals; the lower-case form the module above sends was also accepted when we tried it on 10 Nov 2026, but the manual says values are case-sensitive, so copy keys as ENTSOG publishes them.
The trap is that the key on ENTSOG's map is not the key the flows sit under. Emden (EPT1) is interconnection point ITP-00209, but its flows are four operators' own points: OGE ITP-00080, GUD ITP-00081, Thyssengas ITP-00105 and GTS ITP-00160. /interconnections joins the two: on each row, toOperatorKey, toPointKey and toDirectionKey make the receiving side's pointDirection.
# Which operators receive Norwegian gas, and under which point keys?
curl -s "https://transparency.entsog.eu/api/v1/interconnections?fromCountryKey=NO&limit=-1"
# Join toOperatorKey + toPointKey + toDirectionKey for each row:
# Emden (EPT1), interconnection ITP-00209, is four operators' points:
# DE-TSO-0009ITP-00080entry DE-TSO-0005ITP-00081entry
# DE-TSO-0002ITP-00105entry NL-TSO-0001ITP-00160entry
# Every direction one point key carries:
curl -s "https://transparency.entsog.eu/api/v1/operatorPointDirections?pointKey=ITP-00080&limit=-1"
# The main point on ENTSOG's map (sub-points such as ITP-00080 answer 404 here):
curl -s "https://transparency.entsog.eu/api/v1/connectionPoints?pointKey=ITP-00209"On 10 Nov 2026, interconnections?fromCountryKey=NO listed 15 legs into the EU and the UK. Asking the Norwegian side for its flows finds nothing: Gassco publishes no physical flow on the platform, so Norway's send-out can only be read from the receiving operators' entry rows.
# The Norwegian side: Gassco (NO-TSO-0001) publishes no physical flow.
curl -s -w " HTTP %{http_code}\n" "https://transparency.entsog.eu/api/v1/operationalData?indicator=Physical%20Flow&periodType=day&from=2026-11-01&to=2026-11-01&pointDirection=NO-TSO-0001ITP-00209exit"
# {"message":"No result found"} HTTP 404Observed on transparency.entsog.eu on 10 Nov 2026. SOURCE: ENTSOG TP 10-11-2026 https://transparency.entsog.eu/.
Daily physical flow for one point
# Physical flow at Dornum, OGE's entry leg, gas days 1 to 7 Nov 2026.
# No key, no registration. JSON by default.
curl -s "https://transparency.entsog.eu/api/v1/operationalData?indicator=Physical%20Flow&periodType=day&from=2026-11-01&to=2026-11-07&pointDirection=DE-TSO-0009ITP-00126entry&timeZone=CET&limit=-1"
# The same as CSV: add .csv to the endpoint (.xml and .xlsx work too).
curl -s "https://transparency.entsog.eu/api/v1/operationalData.csv?indicator=Physical%20Flow&periodType=day&from=2026-11-01&to=2026-11-07&pointDirection=DE-TSO-0009ITP-00126entry&timeZone=CET&limit=-1" -o dornum.csvThe answer is a meta block and an operationalData array, one object per row. This is its shape for the request above, values left out:
{
"meta": { "limit": -1, "offset": 0, "count": 7, "total": 8, ... },
"operationalData": [
{
"indicator": "Physical Flow",
"periodType": "day",
"periodFrom": "2026-11-01T06:00:00+01:00",
"periodTo": "2026-11-02T06:00:00+01:00",
"operatorKey": "DE-TSO-0009",
"operatorLabel": "Open Grid Europe",
"pointKey": "ITP-00126",
"pointLabel": "Dornum / NETRA (OGE)",
"directionKey": "entry",
"unit": "kWh/d",
"value": ...,
"flowStatus": "Provisional",
"lastUpdateDateTime": "2026-11-02T08:44:49+01:00",
"isNA": null,
...
},
...
]
}meta.count is the rows you got. meta.total is not a count of rows still to come: here it read 8 for 7 rows. See section 05.
Observed on transparency.entsog.eu on 10 Nov 2026. SOURCE: ENTSOG TP 10-11-2026 https://transparency.entsog.eu/.
ENTSOG API in Python with requests
physical_flow sends one request and turns ENTSOG's 404 for an empty answer into an empty list; by_gas_day keys each value by gas day and pointDirection in GWh/d. Python 3.9 or later, with requests.
from datetime import datetime, timedelta
from zoneinfo import ZoneInfo
import requests
API = "https://transparency.entsog.eu/api/v1/operationalData"
# Norway's five landing points, as the receiving operators report them:
# operatorKey + pointKey + directionKey. Emden (EPT1) is four operators' rows.
LANDINGS = {
"Emden (EPT1)": [
"DE-TSO-0009ITP-00080entry",
"DE-TSO-0005ITP-00081entry",
"DE-TSO-0002ITP-00105entry",
"NL-TSO-0001ITP-00160entry",
],
"Dornum": ["DE-TSO-0009ITP-00126entry"],
"Dunkerque": ["FR-TSO-0003ITP-00045entry"],
"Zeebrugge ZPT": ["BE-TSO-0001ITP-00106entry"],
"Easington": ["UK-TSO-0001ITP-00091entry"],
}
def physical_flow(first_day, last_day, point_directions):
"""Daily Physical Flow rows for gas days first_day to last_day, both included."""
params = {
"indicator": "Physical Flow", # case-sensitive: "physical flow" finds nothing
"periodType": "day",
"from": first_day.isoformat(),
"to": last_day.isoformat(),
"pointDirection": ",".join(point_directions),
"timeZone": "CET",
"limit": -1, # every row, so keep the window to about a month
}
r = requests.get(API, params=params, timeout=70)
if r.status_code == 404 and "No result found" in r.text:
return [] # ENTSOG answers an empty query with HTTP 404
r.raise_for_status()
return r.json()["operationalData"]
def by_gas_day(rows):
"""{gas day: {operatorKey+pointKey+directionKey: GWh/d}}"""
out = {}
for row in rows:
if row["value"] is None:
continue # a row marked not applicable carries no value
gas_day = row["periodFrom"][:10] # starts 06:00 German time that date
leg = row["operatorKey"] + row["pointKey"] + row["directionKey"]
out.setdefault(gas_day, {})[leg] = float(row["value"]) / 1e6 # kWh/d to GWh/d
return outThe last 30 complete gas days at Norway's five landing points
# The gas day in progress runs 06:00 to 06:00 German time and is partial,
# so stop at the one before it.
berlin = datetime.now(ZoneInfo("Europe/Berlin"))
running = (berlin - timedelta(hours=6)).date()
last_day = running - timedelta(days=1)
first_day = last_day - timedelta(days=29)
every_leg = [leg for legs in LANDINGS.values() for leg in legs]
days = by_gas_day(physical_flow(first_day, last_day, every_leg))
for gas_day, legs in sorted(days.items()):
landed = {}
for name, keys in LANDINGS.items():
if all(k in legs for k in keys): # one late operator: no partial sum
landed[name] = sum(legs[k] for k in keys)
print(gas_day, {name: round(gwh) for name, gwh in landed.items()})The sums are yours, not ENTSOG's: Emden is four rows added together, and a day on which one of the four has not published is left out rather than added up short. Credit them as your own calculation from ENTSOG data.
100 rows by default, 60 seconds at most
- 100 rows unless you say otherwise. Every endpoint returns at most 100 rows without
limit.limit=-1returns every row, and ENTSOG warns that it can time out on large sets (manual 2.4.3). - 60 seconds per query. ENTSOG stops any query after 60 seconds and asks for monthly windows, few indicators per call, precise filters and retries with a back-off (manual, Introduction). A month of daily flow for the eight Norwegian legs, 248 rows, came back in about a second on 10 Nov 2026.
- Do not page with offset. On 10 Nov 2026 we asked for two gas days at the eight legs, 16 rows, with
limit=8. The first page held 5 rows, not 8, and the pages atoffset=8and16repeated 5 rows already served. A short page does not mean the end, andmeta.totaldoes not count what is left. Ask for a window small enough to take whole withlimit=-1, or with a limit far above the rows you expect, and treat a full page as cut off, as the module behind the live table does with its limit of 2000. - An empty answer is a 404. A query that matches nothing gets HTTP 404 and
{"message":"No result found"}. A capitalisation slip does that:indicator=physical%20flowfinds nothing wherePhysical%20Flowworks. Treat the 404 as “nothing published” only when you expect nothing; anywhere else it is a hole in your data.
Observed on transparency.entsog.eu on 10 Nov 2026. SOURCE: ENTSOG TP 10-11-2026 https://transparency.entsog.eu/.
06:00 to 06:00 German time, and today is partial
A daily row runs from 06:00 to 06:00 German time. periodFrom shows it as 2026-11-01T06:00:00+01:00 in winter and 2026-09-13T06:00:00+02:00 in summer, so the date part of periodFrom is the gas day. Convert it to UTC and the start moves to 05:00 or 04:00; take the date from the local form, as the code above does.
The manual says timeZone sets how the API reads date filters, and that only WET converts correctly today; CET and others are accepted but may be ignored (manual 2.4.2). For daily rows it made no difference: CET, WET, UCT and no timeZone at all returned the same rows and the same periodFrom.
to can reach the gas day still running, and ENTSOG returns it. At 10:17 German time on 10 Nov 2026, OGE's Emden row for that gas day had about an eighth of the day before's flow. Operators also publish on different lags: at 11:40 German time the same morning, three of the eight Norwegian legs had not yet published gas day 9 Nov. Stop at the day before the running one, and decide what a day with a late operator means for you before you sum it.
Observed on transparency.entsog.eu on 10 Nov 2026. SOURCE: ENTSOG TP 10-11-2026 https://transparency.entsog.eu/.
The same gas under three keys
- Dornum is published more than once. OGE's ITP-00126 and its Dornum GASPOOL ITP-00525 carried the identical value, to the decimal, on every gas day from 1 to 5 Nov 2026, and GUD's ITP-00188 was within 0.1% of them. Add all three and Dornum counts three times. The live table reads ITP-00126 alone.
- Some legs are empty. The three Emden (NPT) legs, ITP-00075, ITP-00086 and ITP-00161, returned “No result found” for October 2026.
- Two Norwegian routes cannot be separated. National Gas reports St Fergus as one figure with UK North Sea gas in it, and Energinet's North Sea Entry, where Baltic Pipe lands, also carries Danish gas from Tyra. The live table leaves both out and says so.
- Operators publish at different hours. A sum across operators for the newest gas day can be short by whole points. Use one gas day for every point rather than each point's newest. Of the two gas days before the one still running, the live table takes whichever more landing points have published, the later on a tie, and names any point that had not published it instead of filling it from another day, so it can show four of five.
Observed on transparency.entsog.eu on 10 Nov 2026. SOURCE: ENTSOG TP 10-11-2026 https://transparency.entsog.eu/.
The first value, a row's history, a country total
The value as first published
The API answers with each row as it stands now. Operators update rows after the gas day they describe, and the answer carries only the latest version and its lastUpdateDateTime: nothing says what the row said before, or whether the update changed the value or only its status. Of the 304 daily Physical Flow rows for the eight Norwegian legs, gas days 1 Oct to 7 Nov 2026, 134 carried a lastUpdateDateTime more than two days after their gas day ended when we read them on 10 Nov 2026, and 61 more than seven days after. GUD's Emden rows for 13 to 15 Sep 2026 were last updated on 21 Oct 2026. The counts were read once and count updates, not changed values. These counts are Voltstack's calculation from ENTSOG data (ENTSOG TP 10-11-2026 https://transparency.entsog.eu/). Totals, sums, averages, ranges and comparisons shown are Voltstack calculations from ENTSOG TP data, not ENTSOG figures, and ENTSOG does not endorse them.
If a backtest or a trade review needs the number as it stood on a given morning, read the rows yourself on a schedule and store each one with the time you read it and its lastUpdateDateTime, and never overwrite. Nothing in the API will rebuild that later.
A total for a country or a route
The flows are per operator and per point. A figure such as “Norway to Europe” is yours to build: choose the legs, take out the duplicates in section 07, decide what to do with the points that mix in other gas, and align every leg on one gas day. Any total you publish is your calculation, and should say so. The live table's total is Voltstack's.
The credit ENTSOG asks for
ENTSOG's Terms and Conditions of Use, TRA0394-16 Rev. 3 of 24 Sep 2018, articles 5.1 and 5.2, allow download, storage and use, and set the citation ENTSOG TP [DD-MM-YYYY] https://transparency.entsog.eu/, with the date you extracted the data. They grant no express right to redistribute, so ask ENTSOG in writing before you republish what you read, serve it to others or feed it to someone else's model. This is a reading of published terms, not legal advice.
On this page the live table carries that credit, dated the day ENTSOG served the quarter that holds its gas day: ENTSOG TP 18-11-2026 https://transparency.entsog.eu/. The observations and counts in sections 01 to 08 were extracted on 10 Nov 2026 and carry ENTSOG TP 10-11-2026 https://transparency.entsog.eu/. Totals, sums and comparisons are Voltstack's own calculations from ENTSOG data. ENTSOG is the source of the data only, and the guide is Voltstack's.
ENTSOG API questions
Is the ENTSOG API free, and does it need a key?
How do I get more than 100 rows from the ENTSOG API?
What is the gas day in ENTSOG data?
Why does the ENTSOG API return “No result found”?
How do I find the pointDirection for a gas flow point?
Does ENTSOG data change after it is published?
How do I cite ENTSOG data?
Pipeline flows next to the rest of the gas balance
Voltstack's workspace shows ENTSOG physical flows at the main EU import points beside EU storage, LNG send-out and power, with the source and the gas day on the panel, so a desk does not have to run its own reader. The 14-day trial opens the workspace; the Voltstack API is in early access, with keys issued on request.
The button opens a 14-day free trial sign-up. Sign-up needs a work email.
The button opens the early-access request on our home page.
More for builders
Sources: ENTSOG Transparency Platform, live table (ENTSOG TP 18-11-2026 https://transparency.entsog.eu/) and observations of 10 Nov 2026 (ENTSOG TP 10-11-2026 https://transparency.entsog.eu/); ENTSOG TP API User Manual v3.0, 1 Oct 2025 (PDF); ENTSOG TP Privacy and Terms and Conditions of Use, TRA0394-16 Rev. 3, 24 Sep 2018 (PDF). Every request on this page was run against https://transparency.entsog.eu/ on 10 Nov 2026, and the observations in sections 01, 02, 03, 05, 06, 07 and 08 and the FAQ are from those runs. The live table is read by the module behind /norway-gas-flows; the quarter that holds its gas day was read at 18 Nov 2026, 00:39 UTC. Totals, sums, averages, ranges and comparisons shown are Voltstack calculations from ENTSOG TP data, not ENTSOG figures, and ENTSOG does not endorse them. ENTSOG accepts no liability for data that has been altered or processed (ENTSOG TP Terms of Use, Art. 5.5).
Disclaimer: Produced by Voltstack Intelligence for information only. ENTSOG changes its API and terms from time to time; check its own documentation before you rely on a parameter here. Corrections to research@voltstack.energy.