Quandl Is Now Nasdaq Data Link
Quandl is now part of Nasdaq Data Link. Nasdaq describes the platform's expansion in its Data Link launch announcement. Existing dataset names alone do not establish whether a dataset is still available or suitable for your application; check its current publisher documentation.
For an oil-price integration, compare the specific series you use, then run a small migration test. OilPriceAPI provides source-timestamped energy and commodity data through a normalized REST API. A matching commodity name does not guarantee the same instrument, observation time, history, or data rights.
Check the dataset before changing providers
| Check | Nasdaq Data Link | OilPriceAPI |
|---|---|---|
| Benchmark and instrument | Check the dataset's publisher, columns, and methodology | Check the commodity code, returned price type, unit, and source |
| API shape | Depends on the dataset; table datasets use the tables API (see Nasdaq Data Link — their docs host has moved and deep links rot) | Latest requests use /v1/prices/latest; archives use the historical endpoint |
| History | Verify the selected dataset's earliest date and update policy | Verify coverage and historical entitlement for each code |
| Freshness | Check the dataset's publication schedule | Read source timestamps; cadence varies by source, market hours, dataset, and plan |
| Access and cost | Check the selected dataset's current subscription terms | Consult current plans and reviewed product facts |
| Data use | Check the publisher's license for your use | Review the Data Usage Policy; API access does not grant ownership or unrestricted redistribution rights |
A practical oil-data migration
1. Inventory the fields your model needs
Record your existing dataset identifier, benchmark, currency, unit, price type, reporting timezone, and expected history. For example, a continuous crude futures series and a spot-price observation need different handling. Do not replace one with the other solely because both say “WTI” or “Brent.”
Browse the current commodity catalog to identify candidate series. Validate them against your existing dataset before changing a production model.
2. Make one authenticated request
Create an account, retrieve its key, and set OILPRICEAPI_KEY in your environment. Run this request from a trusted terminal:
curl --fail-with-body \
'https://api.oilpriceapi.com/v1/prices/latest?by_code=BRENT_CRUDE_USD' \
-H "Authorization: Token $OILPRICEAPI_KEY"
Inspect data.code, data.price, data.currency, data.created_at, and any returned type/source metadata. Use the canonical quickstart for the current response contract. This request establishes connectivity and access; it does not establish equivalence to your old dataset.
3. Compare a bounded historical sample
curl --fail-with-body \
'https://api.oilpriceapi.com/v1/prices/historical?by_code=BRENT_CRUDE_USD&start_date=2026-01-01&end_date=2026-01-31&interval=daily' \
-H "Authorization: Token $OILPRICEAPI_KEY"
Check available dates, missing observations, aggregation, units, and pagination. History depth depends on the series and account entitlement. Follow the historical reference when extending the date range; do not treat a single page of rows as the full archive.
For a spreadsheet evaluation, download the displayed monthly preview. It is a limited preview, not a complete historical export.
4. Handle access and freshness explicitly
| Response | Next step |
|---|---|
| 401 | Check the key and Authorization: Token header |
| 402 or 403 | Check the dataset and history access included in your account |
| 429 | Respect the returned limit/reset information before retrying |
| Empty history | Check the code, requested dates, source coverage, and pagination |
| Older source timestamp | Compare it with the source's publication schedule and your model's freshness requirement |
Keep your previous integration available until a representative sample passes these checks.
Choose a plan around the workflow
The reviewed product facts describe the current trial and Free offer. Pricing is the source for paid-plan terms. Estimate request volume from the number of series and polling schedule, then confirm that the necessary datasets and history are available. A trial or larger request quota does not imply access to every dataset.
Create an account · Compare plans · Historical API reference