Physical and financial distinctions
Separate oil and gas references by the agreed benchmark and contract. Do not mix delivery locations or contract months in an API series without an explicit transformation and roll definition.
Market data · deployment planning
Energy Market Data API
Energy prices depend on product grade, location, delivery period and unit as well as the headline instrument name.
Comparable values
Expose the currency and quotation unit with the data catalogue. Consumer tests should include unit conversion, expiry transitions and a missing contract; numerical values alone do not establish that two energy series are comparable.
Requirements to confirm
- Benchmark and delivery location
- Contract month and expiry
- Currency and quotation unit
- Conversion and roll test cases
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
Integration brief
Energy Market Data API: what to agree before connecting
| Instrument scope | Identify the exact underlying, source identifier, quote currency and intended use. |
|---|---|
| Consumer workflow | List trading platforms, charts, risk tools and applications that need the output. |
| Delivery contract | Agree protocol, quote fields, timestamps, source status and recovery behaviour. |
| Production review | Confirm source rights, integration ownership, test evidence and commercial scope. |
Begin with a consumer and instrument inventory
For energy and commodities, define who consumes the prices and what each system needs to reconstruct a usable quote. An application dashboard, broker platform and historical process can require different delivery rules even when they share one normalized instrument model.
What to test
- Compare instrument definitions before combining or substituting sources.
- Exercise disconnects and confirm the status presented to each consumer.
- Review results with the source, adapter and consuming application owners.
{
"type": "quote",
"symbol": "EURUSD",
"bid": "1.10000",
"ask": "1.10010",
"source_time": "2026-10-18T12:00:00.000Z",
"received_at": "2026-10-18T12:00:00.012Z",
"source_id": "example-source",
"status": "illustrative"
}Illustrative engineering example, not live prices or a published API contract. Confirm field names and delivery rules during integration.