Active Commodity Futures Contracts Snapshot
View all Indian Stock Exchange API endpoints →Returns a snapshot of market data for currently active commodity futures contracts as a JSON array with one object per contract, covering prices, trading volume, open interest, expiry and contract month. The endpoint is a plain GET on /commodities and accepts no query, path or body parameters. No live probe call was recorded for this endpoint, so everything below comes from the source documentation and its bundled example records and has not been verified against a live response. The documentation table names 20 camelCase fields: contractId, dataTimestamp, commoditySymbol, expiryDate, lastTradedPrice, lastTradeQuantity, lastTradeTime, averageTradedPrice, totalVolume, openInterest, openingPrice, highPrice, lowPrice, closingPrice, totalTradedValue, priceUnit, contractSize, contractMonth, priceChange and percentageChange. The bundled example records instead use 26 snake_case keys: id, messageTime, product, expiry, product_month, last_traded_price, last_traded_quantity, last_traded_time, average_traded_price, total_quantity_traded, open_interest, open_price, high_price, low_price, close_price, total_traded_value, price_quotation_unit, quotation_lot, change, per_change, buy_price, buy_quantity, sell_price, sell_quantity, option_type and strike_price. In those records most numeric values are quoted strings, and the sample rows are dated 21 Jun 2024 with AUG2024 and SEP2024 contract months, so they illustrate the shape rather than current data. The result is an informational snapshot, not an execution or licensed tick feed.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/indian-stock-exchange-api/commodity-futures-data-api No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/indian-stock-exchange-api/commodity-futures-data-api?key=<API_KEY>'
Query Result
Use Cases
- A futures-curve view per commodity that plots last traded price against contract month
- An open-interest ranking that surfaces the most crowded contract of each commodity
- A roll-date alert that warns when a contract's expiry date is a few trading days away
- A price-unit normalizer so dashboards do not mix KGS, barrel and other quoting units
- A session snapshot archive keyed by the snapshot timestamp and contract id, used to rebuild intraday history
Frequently asked questions
Does the commodities endpoint take any parameters?
No. It is a single GET on /commodities with no query, path or body parameters. There is no commodity, expiry or date filter, so narrow the array in your own code, for example by the commodity symbol or the contract month.
Will the response use camelCase or snake_case field names?
The source documentation table lists camelCase names such as contractId, commoditySymbol, contractMonth and openInterest, while its bundled example records use snake_case keys such as id, product, product_month and open_interest. No live probe was recorded, so confirm the real key names on your first call and map both spellings defensively.
Are the values numbers or strings?
In the bundled example records most values, including prices, quantities, open interest, lot size and total traded value, are quoted strings such as "6781.00", while change and per_change are numbers. The documentation example shows plain numbers instead. Parse every numeric field explicitly rather than trusting the JSON type.
Does this endpoint return historical commodity data?
The introduction mentions real-time and historical data, but the endpoint itself is documented as a snapshot of currently active contracts and has no date parameter. To build history, store each response together with its snapshot timestamp and contract id.
How should I read the price unit, lot size and traded value?
The example shows BBL and GRMS quotation units and lots of 1, 10 and 100, but the documentation does not explain how a price relates to its unit or in which unit total traded value is expressed. Confirm contract specifications before computing notional amounts, and do not compare prices across different units.
The sample rows are from June 2024. Is the live data that old?
The June 2024 timestamps and AUG2024 and SEP2024 contract months belong to the documentation examples, not to a live response. The endpoint is described as returning currently active contracts, so check the snapshot timestamp in each response, and remember it is an informational snapshot rather than an execution feed.