Abaxx APIabaxx.exchange ↗
Access historical settlement data for LNG futures contracts on Abaxx Exchange. Filter by product code and date. Returns OHLC, volume, open interest, and more.
What is the Abaxx API?
The Abaxx Exchange API provides 2 endpoints for querying historical settlement and market data for LNG futures contracts traded on Abaxx Exchange. The get_historical_data endpoint returns per-contract OHLC prices, settlement values, volume, and open interest across all listed contract months for a given product and date. A companion get_products endpoint exposes the full list of available product codes and the date range of available data.
curl -X GET 'https://api.parse.bot/scraper/63b10a9b-9dc5-4e97-a63e-e689acb9bc33/get_historical_data?date=2026-07-07&product=GOM' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace abaxx-exchange-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Abaxx Exchange LNG futures — discover products, fetch settlements."""
from parse_apis.abaxx_exchange_historical_market_data_api import (
AbaxxExchange, Product_, ProductNotFound,
)
client = AbaxxExchange()
# List available LNG futures products (capped)
for product in client.products.list(limit=5):
print(product.code)
# Construct a product by code and fetch its latest settlements
gom = client.product(code="GOM")
for contract in gom.settlements(limit=3):
print(contract.symbol, contract.settlement, contract.volume)
# Use the enum to pick a specific product and fetch with a date filter
npa = client.product(code=Product_.NPA)
for contract in npa.settlements(date="2026-06-08", limit=3):
print(contract.symbol, contract.expiry, contract.settle_change)
# Typed error handling
try:
bad = client.product(code="INVALID")
bad.settlements(limit=1).first()
except ProductNotFound as exc:
print(f"Product not found: {exc.product}")
print("exercised: products.list / product().settlements / Product_ enum / ProductNotFound error")
Get historical settlement data for LNG futures contracts. Returns all contract months with OHLC prices, settlement, volume, and open interest for a given product and date. When no date is provided, returns data for the latest available trading date. Each product has up to ~24 contract months listed. Fields like open/high/low/close may be '-' when no trades occurred for that contract month.
| Param | Type | Description |
|---|---|---|
| date | string | Trading date in YYYY-MM-DD format. If omitted, returns the latest available date. |
| product | string | Product code to filter by. Accepted values: GOM, NPA, CP1, RD1, GWM, EWM, UWM, FWM, NWM, SWM, GSM, NSS, LCS, LCR, LCB, GKS, SSP. If omitted, returns data for all products. |
{
"type": "object",
"fields": {
"data": "array of contract objects with fields: product, symbol, contract_month, trade_date, expiry, open, high, low, close, settlement, settle_change, volume, open_interest",
"date": "string - the trading date of the returned data in YYYY-MM-DD format",
"product": "string - product code filter applied, or ALL if no filter",
"total_rows": "integer - number of contract rows returned"
},
"sample": {
"data": {
"data": [
{
"low": "15.70",
"high": "15.70",
"open": "15.70",
"close": "15.70",
"expiry": "2026-07-01",
"symbol": "GOMQ26",
"volume": 202,
"product": "GOM",
"settlement": "15.70",
"trade_date": "2026-06-10",
"open_interest": "0",
"settle_change": "0.00",
"contract_month": "GOMQ26 (Aug)"
},
{
"low": "14.82",
"high": "14.83",
"open": "14.83",
"close": "14.82",
"expiry": "2026-08-03",
"symbol": "GOMU26",
"volume": 202,
"product": "GOM",
"settlement": "14.82",
"trade_date": "2026-06-10",
"open_interest": "0",
"settle_change": "0.02",
"contract_month": "GOMU26 (Sep)"
}
],
"date": "2026-06-10",
"product": "GOM",
"total_rows": 24
},
"status": "success"
}
}About the Abaxx API
What the API Covers
The Abaxx Exchange lists LNG (liquefied natural gas) futures across multiple regional and product-specific codes. This API surfaces the end-of-day settlement data that Abaxx publishes on its market data page, giving you access to historical records spanning the full date range available on the exchange.
get_historical_data Endpoint
The primary endpoint, get_historical_data, accepts two optional parameters: date (a trading date in YYYY-MM-DD format) and product (one of 14 accepted product codes including GOM, NPA, CP1, RD1, GWM, EWM, UWM, FWM, NWM, SWM, GSM, NSS, LCS, and L). Omitting date returns the latest available trading date. Omitting product returns rows for all products. Each row in the data array contains the fields product, symbol, contract_month, trade_date, expiry, open, high, low, close, and settlement, along with volume and open interest. The response also includes a total_rows count and echoes back the date and product filter applied.
get_products Endpoint
The get_products endpoint takes no inputs and returns two things: an array of all valid product code strings that can be passed to get_historical_data, and a date_range object with min_eod and max_eod fields indicating the earliest and latest trading dates for which settlement data exists. This is useful for building date-range pickers or validating input before querying historical data.
Data Freshness and Coverage
Data reflects end-of-day settlement records as published by Abaxx Exchange. The get_products endpoint's max_eod field is the authoritative indicator of how current the available data is. Coverage is limited to products actively listed on Abaxx Exchange; no intraday tick or order book data is exposed.
The Abaxx API is a managed, monitored endpoint for abaxx.exchange — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when abaxx.exchange changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official abaxx.exchange API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track daily settlement prices for specific LNG futures contract months by querying
get_historical_datawith a product code likeGOMorNPA. - Build a time-series chart of OHLC values for an LNG futures product across its full historical date range.
- Monitor open interest changes across contract months to gauge market participation trends on Abaxx Exchange.
- Validate available product codes and data freshness before running bulk historical queries using the
get_productsendpoint. - Construct a settlement price database for LNG futures to feed quantitative models or spread analysis.
- Alert systems that detect when volume or open interest for a given contract month crosses a threshold on a new trading date.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Abaxx Exchange have an official developer API?+
What does the `product` parameter in `get_historical_data` control, and what happens if I omit it?+
product code — such as GOM, NPA, or CP1 — filters the response to rows for that single product. Omitting the parameter returns all available products for the specified date, and the response will reflect ALL in the product field. The total_rows field tells you how many contract rows were returned.Does the API return intraday or tick-level data for LNG futures?+
How do I find out what date range of historical data is available?+
get_products. The response includes a date_range object with min_eod and max_eod fields that indicate the earliest and latest trading dates for which settlement data exists. Use max_eod to confirm data freshness before querying.