Will there be a separate gas futures endpoint?

No. Natural gas futures stay under /v1/futures/* to avoid duplicate endpoint surface area.

Can I join futures to storage?

Yes. Use the futures endpoint for contract data and /v1/natural-gas/storage for weekly storage context.

Futures framework

Use the futures routes for Henry Hub natural gas contracts, curves, historical data, OHLC, intraday data, and spread workflows.

Contract coverage

Natural gas futures

Check the returned contract month and observation timestamp.

Source: CME Group Henry Hub Natural Gas futures contract reference
Last source update: Contract reference verified July 3, 2026; endpoint responses include contract and timestamp fields where available.
Cadence: Exchange-session dependent futures data through the existing futures package.
Caveat: Futures data is separate from spot price and storage data. Do not add a duplicate gas futures route.

futures

Returns supported natural gas futures data through the established futures route.

curl "https://api.oilpriceapi.com/v1/futures/natural-gas" \
  -H "Authorization: Token YOUR_API_KEY"

futures

Returns supported curve observations without creating a separate gas futures surface.

curl "https://api.oilpriceapi.com/v1/futures/natural-gas/curve" \
  -H "Authorization: Token YOUR_API_KEY"

1Use /v1/futures/natural-gas for supported contract data.
2Use existing futures subroutes for history, OHLC, intraday, spreads, and curve workflows.
3Join to storage or spot prices only after checking each response timestamp.

contract

expiration

price

settlement

open interest

volume

timestamp

Use storage data when futures reaction needs weekly inventory context.

Use spot benchmark price data alongside futures curve data.

Add Permian basis context where Waha affects your workflow.

Start with the existing API surface and keep source timestamps attached to every gas workflow.