First-call proof
Make your first API request in under 10 minutes
Run a real request from this page first. The demo route answers without a key and without an account, so you can see the response shape before you decide anything. Once that is working, the same workflow drives spreadsheets, alerts, widgets, or your own internal tools.
Try the API
No API key required
curl --fail-with-body --max-time 10 \
"https://api.oilpriceapi.com/v1/demo/prices"1. Copy your API key
Use your dashboard key in the Authorization header. Do not paste API keys into public code, shared documents, or logs.
2. Run one request
Start with /v1/prices/latest?by_code=BRENT_CRUDE_USD and keep the first call focused on a single success path.
3. Confirm JSON
Check that the response is valid JSON before adding spreadsheets, alerts, widgets, or internal tools.
Run one request
Confirm a valid JSON response
Keep the first call narrow: send one request, confirm the response shape, then decide which workflow should come next.
curl "https://api.oilpriceapi.com/v1/prices/latest?by_code=BRENT_CRUDE_USD" \
-H "Authorization: Token YOUR_API_KEY"No key yet
Use the supported demo route
OilPriceAPI does not issue special test keys. Use the keyless demo endpoint or fixtures for automated tests, and keep customer keys out of CI.
curl "https://api.oilpriceapi.com/v1/demo/prices"New accounts receive a 7-day core commodity api trial with 10,000 requests and no credit card. Afterward, Free includes 50 requests per day. Dataset access and limits vary by plan, source, and account entitlement.
Choose the workflow you want next
Build from one working request
Find codes and latest prices
Confirm the commodity code and response fields before adding more symbols or sources.
If a code, region, or source is missing, send the intended workflow instead of guessing.
Open code guide
Use OilPriceAPI in Excel
Use the add-in formula path after the first API call works outside the spreadsheet.
Save the key in the OilPrice pane. Do not paste API keys into worksheet cells.
Open Excel guide
Understand historical rows
Check date, price, source/type fields, and dataset semantics before using rows in analysis.
Do not treat a row as an official close, settlement, or complete history unless that dataset supports it.
Open historical guide
Choose futures or latest prices
Use futures-specific pages when contract month, OHLC, settlement-style fields, or curve semantics matter.
Latest-price endpoints are not a substitute for exchange-grade futures feeds or resale-ready market data.
Open futures guide
Connect a customer-owned source
Use the marine connector path when provider access, ports, grades, or source-specific terms matter.
Provider rights, ports, grades, history, and usage terms need source-specific verification.
Open connector guide
Check data fit before plan fit
Confirm the commodity, region or source, workflow, and expected request volume before upgrading.
Unknown or gated data should route to support verification before upgrade pressure.
Review plan fit