Hubs LNG Regas

The Hubs LNG Regas endpoints allow you to pull active and inactive regas capacity posts from the Spark Hubs Regas platform (Europe). This covers outright posts (bids and offers) and tenders (buy and sell) across four regions: Northwest Europe (nwe), Southwest Europe (swe), East Mediterranean (emd) and the Baltic (bal).

Looking to pull Hubs Regas data?

Visit our Python Code Examples section to download our Hubs Regas code sample, the quickest way to start pulling Hubs Regas data.

Hubs Regas Subscription Required

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

Active Posts

/v1.0/lng/hubs/regas/active/

Call this endpoint to retrieve active Hubs Regas posts, including both outright posts and tenders.

Parameters

• region (optional)
  • Filter posts by region. A post is returned if any of its regions match.
  • Available values: nwe, swe, emd, bal
• interest-type (optional)
  • Filter posts by post type.
  • Available values: outright, tender

Data can be retrieved in JSON or CSV format, although metadata is only available in the JSON response. If there are no active posts, an empty list is returned.

Inactive Posts

/v1.0/lng/hubs/regas/inactive/

Call this endpoint to retrieve all inactive Hubs Regas posts, including both outright posts and tenders. This includes posts that have expired, tenders that have ended and posts removed by the poster, all of which are returned with status set to expired. Active posts are not included in this response - use the Active Posts endpoint to retrieve those.

Parameters

• region (optional)
  • Filter posts by region. A post is returned if any of its regions match.
  • Available values: nwe, swe, emd, bal
• interest-type (optional)
  • Filter posts by post type.
  • Available values: outright, tender

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

Reference Data

/v1.0/lng/hubs/regas/reference-data/

Call this endpoint to retrieve the available regions and, for each region, the post types (outright, tender) that can be used to filter the Active and Inactive Posts endpoints.

The lookup of terminal UUIDs to terminal names is returned in the metaData.terminals field of the Active and Inactive Posts endpoints, and covers every Hubs Regas terminal.

Parameters

This endpoint has no parameters to specify.

Data can be retrieved in JSON or CSV format.

Response Fields

The Active and Inactive Posts endpoints return the same fields. CSV headers are the JSON field names with the first letter capitalised and acronyms in upper case (e.g. postedAtUtc becomes PostedAtUTC). Fields that only apply to tenders are empty for outright posts.

JSON field	CSV column(s)	Description
postId	PostID	Unique post ID, e.g. LNG-RGS-NWE-O-0001
hubRegions	HubRegions	Region(s) of the post's terminals. A post can belong to two regions (e.g. Deutsche Ostsee is in both nwe and bal)
interestType	InterestType	outright or tender
orderType	OrderType	bid or offer for outright posts, buy or sell for tenders
status	Status	active or expired
tenderPhase	TenderPhase	Tenders only: published, live or end
posterOrgName	PosterOrgName	The poster's organisation, or Anonymous
posterUserName	PosterUserName	The poster's user name. Only populated for posts made by your own organisation, otherwise empty
connectionsCount	ConnectionCount	Number of counterparties that have responded to the post
terminals	TerminalUUIDs, TerminalNames	The post's terminals, as a UUID to name map. In the CSV, two comma-separated columns in matching order
terminalsAreHidden	TerminalsAreHidden	true if the poster has hidden the terminals
windows[].dateType	WindowDateType	How the vessel arrival window was entered: single (one date), range, window-1h (1st to 15th of the month), window-2h (16th to month end) or month
windows[].startDate, windows[].endDate	WindowStartDate, WindowEndDate	First and last date of the window. Both are always provided. For single, the end date equals the start date
windows[].outrightCargoCount	WindowOutrightCargoCount	Number of cargoes in the window
windowsAreHidden	WindowsAreHidden	true if the poster has hidden the windows
quantityMin, quantityMax	QuantityMin, QuantityMax	Discharge quantity range. Empty if not set
quantityUnit	QuantityUnit	mmbtu, tbtu, m3 or gwh
quantityIsHidden, quantityIsFlexible	QuantityIsHidden, QuantityIsFlexible	Whether the quantity is hidden, and whether it is flexible
slotType	SlotType	firm or optional
serviceTypes	ServiceTypes	Services included: berth, unload, storage, regas-and-send-out, entry-capacity
tua	TUA	Terminal Use Agreement: yes, no or empty. On offer and sell posts, whether the counterparty is required to hold a TUA. On bid and buy posts, whether the poster has a TUA in place
priceType	PriceType	indicative for outright posts, reserve for tenders
priceStructure	PriceStructure	total-fixed or premium-to-base-tariff
priceFixedValue	PriceFixedValue	The price, when priceStructure is total-fixed
pricePremiumValue	PricePremiumValue	The premium to the terminal's base tariff, when priceStructure is premium-to-base-tariff
priceUnit	PriceUnit	eur-per-mwh, usd-per-mmbtu, lump-sum-eur or lump-sum-usd. Lump sums are a total amount for the slot, not a per-unit price
priceIsHidden	PriceIsHidden	true if the poster has hidden the price
otherInfo, otherInfoIsHidden	OtherInfo, OtherInfoIsHidden	Free-text notes from the poster, and whether they are hidden
postedAtUtc	PostedAtUTC	When the post was created (UTC)
postValidUntilUtc	PostValidUntilUTC	Outright posts: when the post expires. Tenders: the bidding deadline (UTC)
postLastUpdatedAtUtc	PostLastUpdatedAtUTC	When the post was last updated (UTC)
tenderLiveAtUtc	TenderLiveAtUTC	Tenders only: when the tender went live (UTC)

A few things to note when working with the data:

• One CSV row per window. A post with several vessel arrival windows (e.g. one per month) has one CSV row per window, with the post's other fields repeated. In JSON, the windows are a list within the post.
• Numbers are returned as strings in JSON (e.g. "1.780") to preserve their precision. Convert them before doing calculations.
• Hidden fields are empty. When the poster hides a field, its value is empty (null in JSON) and the matching ...IsHidden field is true.
• Metadata. The JSON metaData includes asOf (the time of your request, UTC), any filters you applied, and terminals, the UUID to name lookup for all Hubs Regas terminals.