Energy Prices API

About the Energy Prices API

An oil price and energy commodity API built on the U.S. Energy Information Administration's daily spot price series: WTI at Cushing, Brent, Henry Hub natural gas, conventional gasoline in New York Harbor and on the Gulf Coast, RBOB gasoline in Los Angeles, ultra-low sulfur diesel in New York Harbor and on the Gulf Coast, CARB diesel in Los Angeles, No. 2 heating oil, Mont Belvieu propane and Gulf Coast jet fuel. These are daily closing assessments that EIA publishes a few days in arrears; they are not live or futures quotes.

Every plan gets the latest close, the previous close, the daily change in dollars and percent, and unit conversion: crude and products per barrel, gallon or liter, natural gas per MMBtu, therm or megawatt-hour. Paid plans add the 52-week high and low with their dates, several benchmarks in one call, any past date back to 1986, and a daily or weekly price history for charts and backtests.

How it works

A scheduled collector reads twelve daily spot price series from the U.S. Energy Information Administration's open data API twice a day and stores every close since 1986 (the series start at different dates; Henry Hub begins in 1997, ultra-low sulfur diesel in 2006). Requests are served from that store, never from EIA live. The data is public domain; source: U.S. Energy Information Administration, Spot Prices for Crude Oil and Petroleum Products and Natural Gas Spot and Futures Prices.

price is the close on date and previousClose the close on the trading day before it; change is the difference and changePercent the same as a percent of the previous close. high52w and low52w are the highest and lowest closes in the 364 days up to date. EIA publishes closing assessments a few days after the trading day, so date usually trails today by two to five days. These are spot prices, not futures settlements or live quotes.

Crude is published per barrel, refined products and propane per gallon and natural gas per MMBtu. unit converts with 42 gallons per barrel, 3.785411784 liters per gallon, 10 therms per MMBtu and 3.412141633 MMBtu per MWh. history returns closes from days - 1 calendar days before date through date; weekly keeps the last close of each Monday-to-Sunday week.

What people use it for

Fuel Surcharge Calculators

Freight and airline tools tie surcharges to the daily diesel or jet fuel spot close and its weekly average, recalculated automatically as the benchmark moves.

Energy Cost Dashboards

Finance teams chart WTI, Brent and Henry Hub side by side in one call, with daily change and 52-week range for context.

Utility and Heating Estimates

Home energy apps convert Henry Hub gas to therms and heating oil to gallons to estimate the wholesale cost behind a household bill.

Backtests and Research

Analysts pull years of weekly closes for crude and products to study crack spreads, seasonality and price shocks.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/energyprices

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Optional

1
2

curl "https://api.apiverve.com/v1/energyprices?benchmark=wti&unit=gallon&date=2025-06-13&history=daily&days=30" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/energyprices

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

{
  "status": "ok",
  "error": null,
  "data": {
    "count": 1,
    "date": "2026-11-11",
    "prices": [
      {
        "benchmark": "wti",
        "name": "WTI Crude Oil",
        "product": "crude oil",
        "location": "Cushing, OK",
        "currency": "USD",
        "unit": "barrel",
        "nativeUnit": "barrel",
        "price": 89.62,
        "date": "2026-11-11",
        "previousClose": 89.62,
        "previousDate": "2026-11-10",
        "change": 0,
        "changePercent": 0,
        "changeDirection": "unchanged",
        "high52w": 114.58,
        "high52wDate": "2026-04-07",
        "low52w": 55.44,
        "low52wDate": "2025-12-16"
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Energy Prices form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Energy Prices API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1Data refreshed daily