Gas Transit

The Gas Transit endpoints allow you to pull Spark's gas transit cost data across European routes.

Looking to pull Gas Transit data?

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

Gas Transit API Subscription Required

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

Reference Data

/v1.0/gas/transit/reference-data/

The Gas Transit Reference Data endpoint returns the list of available transit routes, each defined by an origin and a destination, along with their respective countries.

• Origin
• Destination
• Origin Country
• Destination Country

Costs

/v1.0/gas/transit/costs/

Call this endpoint to retrieve gas transit cost data, including a full cost component breakdown.

Parameters

• unit (required)
  • The unit for cost values in the response.
  • Available values: eur-per-mwh, usd-per-mmbtu, p-per-therm
• 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.
• type (optional)
  • The transit capacity type.
  • Available values: firm, interruptible
• product (optional)
  • The product granularity.
  • Available values: annual, quarterly, monthly, daily
• start (optional)
  • Start date for the data range.
  • Format: yyyy-mm-dd
• end (optional)
  • End date for the data range.
  • Format: yyyy-mm-dd
  • The start/end date range has an upper limit of 1 year.
• limit (optional)
  • Integer value to set an upper limit on the number of release dates returned.
• offset (optional)
  • Integer value to set from where to start returning data.
  • limit must be greater than offset when both are provided.

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.

Costs Changelog

/v1.0/gas/transit/costs/changelog/

Call this endpoint to retrieve the log of changes applied to gas transit cost data, so you can track how a published tariff has evolved over time. Each entry returns one row per effective period affected by the change.

Values are returned in the unit published by the TSO, which is why there is no unit parameter on this endpoint.

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.
• 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
• limit (optional)
  • Integer value to set an upper limit on the number of entry dates returned.
• offset (optional)
  • Integer value to set from where to start returning data.
  • limit must be greater than offset when both are provided.

Entries are returned with the most recent entry date first.

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.

Tariff Calendar

/v1.0/gas/transit/costs/calendar/

Call this endpoint to retrieve the forward-looking tariff publication calendar: for each transmission system operator, when its transport tariff is next expected to change, and whether the value currently published is the operator's own final tariff or a Spark estimate awaiting confirmation. It is the forward-looking counterpart to the Costs Changelog - once a change is confirmed it is posted to the changelog and the calendar row advances to the following period.

Each entry returns one row per operator, including the route and regulator it belongs to, its tariff year convention, the end of the period Spark has confirmed tariffs for (currentPeriodEnds), the expected date range of the next change (nextChangeStart / nextChangeEnd) and a plain-English summary of what is changing.

An operator that spans two hubs - an interconnector, for example - returns them as its origin and destination. An operator that runs within a single hub returns that same hub as both, so it is matched by a filter on either side.

The calendar is a snapshot of the current state rather than a history, so a single asOf date is returned in the metadata for the whole response.

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.
• status (optional)
  • Filter results by publication status.
  • Available values: expected, provisional
  • expected means no tariff has been loaded for the next period yet; provisional means a Spark estimate is loaded and is awaiting the regulator's final tariff.

The calendar holds one row per operator and no history, so there is nothing to page through: every response is the complete set of operators matching your filters. This endpoint takes no start, end, limit or offset parameter.

Entries are returned with the earliest expected change first. Operators with no scheduled change are returned last.

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