Skip to content

Gas Transit Capacity ​

The Gas Transit Capacity endpoints allow you to pull Spark's pipeline capacity data across European gas transit routes: the Technical, Booked and Available capacity of each route, as shown on the Spark platform.

Looking to pull Gas Transit Capacity data?

Visit our Python Code Examples section to download our Gas Transit Capacity code sample, the quickest way to start pulling Gas Transit Capacity data.

Gas Transit API Subscription Required

Contact us to discuss our Premium plans at commercial@sparkcommodities.com

Historical data is available from 18th August 2026. Gas Transit Capacity data is published daily at 00:00 GMT.

Monthly Capacity ​

/v1.0/gas/transit/capacities/monthly/

Call this endpoint to retrieve route capacity by delivery month. Each row is one release, route, capacity type and delivery month, with the minimum, mean and maximum of the daily route values in that month, and the number of gas days behind the mean.

Parameters ​

  • origin (optional)
    • Filter results by route origin.
    • See the Reference Data endpoint for available values.
  • destination (optional)
    • Filter results by route destination.
    • See the Reference Data endpoint for available values.
  • route-id (optional)
    • Filter results by route ID, e.g. psv-sivtp.
    • See the Reference Data endpoint for available values.
  • type (optional)
    • The transit capacity type.
    • Available values: firm, interruptible
  • unit (optional)
    • The unit for capacity values in the response.
    • Available values: gwh-per-day (default)
  • start (optional)
    • Start date for the data range, applied to the release date.
    • Format: yyyy-mm-dd
  • end (optional)
    • End date for the data range, applied to the release date.
    • Format: yyyy-mm-dd
    • start must be earlier than end, and the start/end date range has an upper limit of 1 year.
    • start/end cannot be combined with limit.
  • limit (optional)
    • Integer value to set an upper limit on the number of release dates returned, starting from the latest release.
    • Maximum value is 260.
  • offset (optional)
    • Integer value to set how many of the most recent release dates to skip.

Example URL: /v1.0/gas/transit/capacities/monthly/?route-id=psv-sivtp&type=firm&start=2026-11-03&end=2026-11-05

Data can be retrieved in JSON or CSV format, although metadata is only available in the JSON response. If no data is available for the requested filters or dates, an empty list is returned.

Pulling every route

To retrieve every route for the latest release, leave out the route filters and use limit=1. Requests without route filters return a large amount of data per release, so requests covering many releases should filter by route-id, or by origin and destination. Requests whose response would be too large return an error asking you to narrow the date range or filters.

Unlimited access to historical data is only available to those with a premium subscription - trial users will only have access to 2 weeks' worth of data.

Daily Capacity ​

/v1.0/gas/transit/capacities/daily/

Call this endpoint to retrieve route capacity by gas day. Each row is one release, route, capacity type and gas day. A release runs from the gas day after the release date to the end of its last delivery month. Each row also gives the binding leg (exit, ic or entry): the leg of the route that sets the route value on that gas day.

Parameters ​

This endpoint takes the same parameters as Monthly Capacity, plus:

  • gas-day-start (optional)
    • First gas day to return within each release.
    • Format: yyyy-mm-dd
  • gas-day-end (optional)
    • Last gas day to return within each release.
    • Format: yyyy-mm-dd

start and end filter the release dates, while gas-day-start and gas-day-end filter the gas days inside each release. For example, start=2026-11-02&end=2026-11-06&gas-day-start=2026-12-01&gas-day-end=2026-12-31 returns the December gas days from each release in the first week of November.

A single release holds around 42,000 rows across all routes, so this endpoint limits how much can be requested in one call:

  • With no start/end and no limit, the latest release is returned.
  • Without a route filter (route-id, or both origin and destination), one release is returned per call. Use limit=1, with offset to step back through earlier releases. start/end are not accepted.
  • With a route filter, the start/end date range has an upper limit of 31 days, and limit has a maximum value of 23.

Example URL: /v1.0/gas/transit/capacities/daily/?route-id=psv-sivtp&start=2026-11-02&end=2026-11-06&gas-day-start=2026-12-01&gas-day-end=2026-12-31

Data can be retrieved in JSON or CSV format, although metadata is only available in the JSON response. If no data is available for the requested filters or dates, an empty list is returned.

Unlimited access to historical data is only available to those with a premium subscription - trial users will only have access to 2 weeks' worth of data.

Monthly Override Impact ​

/v1.0/gas/transit/capacities/monthly/override-impact/

Call this endpoint to see the effect of Spark overrides on monthly route capacity. Each row gives the route value twice, side by side: the ENTSOG value, calculated with every Spark override removed, and the Spark value, which is the value published on the Monthly Capacity endpoint.

Rows are returned only for the routes and delivery months where a Spark override is in place on any leg of the route. Every figure is returned for those rows, including figures the override does not change, where the two values are equal.

Parameters ​

This endpoint takes the same parameters as Monthly Capacity, plus:

  • indicator (optional)
    • Filter results by capacity figure.
    • Available values: technical (firm only), booked, available

Example URL: /v1.0/gas/transit/capacities/monthly/override-impact/?route-id=psv-sivtp&indicator=available&limit=1

Data can be retrieved in JSON or CSV format, although metadata is only available in the JSON response. A release with no override in place returns an empty list.

Unlimited access to historical data is only available to those with a premium subscription - trial users will only have access to 2 weeks' worth of data.

Daily Override Impact ​

/v1.0/gas/transit/capacities/daily/override-impact/

Call this endpoint to see the effect of Spark overrides on daily route capacity. It works in the same way as Monthly Override Impact, with one row per gas day, and the Spark value is the value published on the Daily Capacity endpoint.

Parameters ​

This endpoint takes the same parameters as Daily Capacity, with the same limits per call, plus:

  • indicator (optional)
    • Filter results by capacity figure.
    • Available values: technical (firm only), booked, available

Example URL: /v1.0/gas/transit/capacities/daily/override-impact/?route-id=psv-sivtp&indicator=available&limit=1&gas-day-start=2027-01-01&gas-day-end=2027-01-31

Data can be retrieved in JSON or CSV format, although metadata is only available in the JSON response. A release with no override in place returns an empty list.

Unlimited access to historical data is only available to those with a premium subscription - trial users will only have access to 2 weeks' worth of data.

Override Log ​

/v1.0/gas/transit/capacities/overrides/log/

Call this endpoint to retrieve the log of every Spark override: each one added, updated or removed, with the reason for it and a link to the source. Each entry returns one row per period and route affected.

Values in the log are for a single leg (one operator, direction and figure), not for the whole route. Each row gives the ENTSOG value at the time of the override, the new Spark value and, for an update or removal, the previous Spark value. To see the effect on the route, use the Override Impact endpoints.

Parameters ​

  • origin (optional)
    • Return the overrides that feed routes from this origin.
    • See the Reference Data endpoint for available values.
  • destination (optional)
    • Return the overrides that feed routes to this destination.
    • See the Reference Data endpoint for available values.
  • route-id (optional)
    • Return the overrides that feed this route, e.g. psv-sivtp.
    • See the Reference Data endpoint for available values.
  • tso (optional)
    • Filter results by transmission system operator code, e.g. plinovodi. The codes are returned in the response.
  • type (optional)
    • The transit capacity type.
    • Available values: firm, interruptible
  • indicator (optional)
    • Filter results by the figure that was overridden.
    • Available values: technical, total, booked, available
    • total applies to interruptible capacity.
  • change-type (optional)
    • Filter results by the type of change.
    • Available values: new, update, removed
  • start (optional)
    • Start date for the data range, applied to the entry date.
    • Format: yyyy-mm-dd
  • end (optional)
    • End date for the data range, applied to the entry date.
    • Format: yyyy-mm-dd
    • start must be earlier than end, and the start/end date range has an upper limit of 1 year.
    • start/end cannot be combined with limit.
  • limit (optional)
    • Integer value to set an upper limit on the number of entry dates returned, starting from the latest entry date.
    • Maximum value is 260.
  • offset (optional)
    • Integer value to set how many of the most recent entry dates to skip.

Entries are returned with the most recent entry date first.

Example URL: /v1.0/gas/transit/capacities/overrides/log/?route-id=psv-sivtp

Data can be retrieved in JSON or CSV format, although metadata is only available in the JSON response.

Unlimited access to historical data is only available to those with a premium subscription - trial users will only have access to 2 weeks' worth of data.