API workflow guardrail
Latest prices start with a valid code and one working request
Before you build a dashboard, spreadsheet, alert, or app, confirm the commodity code, endpoint family, and response fields that your workflow depends on.
First fit check
Treat a code as confirmed only after the endpoint returns the fields your workflow needs.
Start with one commodity code, not a broad basket.
Inspect the JSON response before adding spreadsheets, widgets, alerts, or internal tools.
Route futures, historical, and source-specific needs to the endpoint family built for that workflow.
Start narrow
Make one latest-price request
Use an authenticated request and a single code first. If the response does not contain the code, source, timestamp, or field shape you need, treat that as a data-fit question before upgrading or building around it.
Request shape
Replace the code with the supported benchmark you are testing.
curl "https://api.oilpriceapi.com/v1/prices/latest?by_code=BRENT_CRUDE_USD" \
-H "Authorization: Token YOUR_API_TOKEN" \
-H "Content-Type: application/json"Choose the right endpoint family
Latest, historical, and futures data answer different questions
If the request is about contract month, date ranges, source conventions, or external-use requirements, do not force it through the first latest-price endpoint. Route the workflow first.
Latest benchmark workflow
Use the latest-price endpoint when your workflow needs a supported current benchmark value and the response fields are a fit.
Historical research
Use historical guides when your workflow depends on date ranges, daily rows, raw observations, or row semantics.
Futures and contracts
Use futures-specific pages when contract month, front month, OHLC, settlement, or curve semantics matter.
Do not assume
These are the common places where integrations drift into the wrong endpoint or unsupported claim.
Every requested symbol, source, or region is available.
Every endpoint exposes identical timestamp, source, or freshness fields.
A dated futures contract belongs on a futures-specific path, not a generic latest-price path.
A plan upgrade solves a data-fit or source/licensing question by itself.
If a code or source is missing
Send enough context for support to verify data fit without guessing.
Share the details below. We can confirm whether the data is supported, should use another endpoint family, or needs a scoped source/package review.
commodity or market you need
region, source, or benchmark convention if known
code and endpoint you tried
intended workflow, such as app, spreadsheet, alert, or dashboard
approximate UTC time of the request
Next workflow
Confirm the first response, then build the workflow
Once a code and endpoint are verified, route to Excel, historical research, futures, alerts, widgets, or plan review with fewer support loops.