Hubs LNG Cargo

The Hubs LNG Cargo endpoints allow you to pull active and inactive LNG cargo posts from the Spark Hubs platform, including both swap and outright posts across multiple regions.

Looking to pull Hubs data?

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

Hubs API Subscription Required

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

For a full definition of all response data fields, please refer to our Hubs API Data Field Definitions document

Active Posts

/v1.0/lng/hubs/cargo/active/

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

Parameters

• unit (required)
  • The unit for quantity values in the response.
  • Available values: mmbtu, m3
• incoterm (optional)
  • Filter posts by incoterm.
  • Available values: fob, des
• region (optional)
  • Filter posts by region.
  • See the Reference Data endpoint for available values.

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

Inactive Posts

/v1.0/lng/hubs/cargo/inactive/

Call this endpoint to retrieve all inactive (expired) Hubs posts, including both swap and outright posts. Active posts are not included in this response - use the Active Posts endpoint to retrieve those.

Parameters

• unit (required)
  • The unit for quantity values in the response.
  • Available values: mmbtu, m3
• incoterm (optional)
  • Filter posts by incoterm.
  • Available values: fob, des
• region (optional)
  • Filter posts by region.
  • See the Reference Data endpoint for available values.

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

Reference Data

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

Call this endpoint to retrieve reference data for the Hubs platform, including available regions, incoterms, and slot types.

Parameters

This endpoint has no parameters to specify.

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