Natural gas futures stay inside the existing futures framework.
The gas MVP does not create a duplicate gas futures surface. Use the existing futures routes for Henry Hub natural gas contracts, curves, historical data, OHLC, intraday data, and spread workflows.
Validated demand for natural gas futures queries.
All gas futures calls remain in futures analytics.
Avoids duplicate futures endpoints and docs drift.
Source and caveat
- 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.
API example
Natural gas futures
futuresReturns 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"Natural gas futures curve
futuresReturns 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"Workflow fit
- 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.
Fields to expect
Measurement built into this launch slice
Signup and pricing CTAs preserve utm_source=data_page, utm_medium=gas_intelligence, and utm_content values specific to this page and CTA location.
Ready to test this workflow?
Start with the existing API surface and keep source timestamps attached to every gas workflow.