Migration: calling the API directly
This guide is for customers who call the Timeseries API from their own code, without our
Python library. The API is moving to a new address, and the paths gain a version. We stop
supporting the old addresses, api.volueinsight.com and api.wattsight.com, on the date in the timeline.
What changes
Section titled “What changes”- The host:
api.volueinsight.comandapi.wattsight.combecomedata-forecasts.volue.com. - The path: insert
/v1/timeseriesafter/apiin every path. - A few endpoints are renamed. They are marked in the endpoint mapping.
Request parameters, query strings and response bodies do not change. Authentication does not change.
GET https://api.volueinsight.com/api/series/12345?from=2026-11-01&to=2026-11-02GET https://data-forecasts.volue.com/api/v1/timeseries/series/12345?from=2026-11-01&to=2026-11-02Terms used on this page
Section titled “Terms used on this page”| Term | Example | Where you use it |
|---|---|---|
| Hostname, or FQDN (fully qualified domain name) | data-forecasts.volue.com |
Firewall and proxy rules |
| Base URL (the web address your calls start from) | https://data-forecasts.volue.com/api/v1/timeseries |
Your code or config |
| Endpoint path | /series/{id} |
Your code, and the endpoint reference |
Endpoint mapping
Section titled “Endpoint mapping”All new paths are on https://data-forecasts.volue.com.
Today (on api.volueinsight.com) |
New | Note |
|---|---|---|
/api/curves |
/api/v1/timeseries/curves |
Curve search |
/api/curves/get |
/api/v1/timeseries/curves/get |
Single curve by name or id |
/api/curves/{id}/access |
/api/v1/timeseries/curves/{id}/access |
|
/api/series/{id} |
/api/v1/timeseries/series/{id} |
|
/api/series/tagged/{id} |
/api/v1/timeseries/series/tagged/{id} |
|
/api/series/tagged/{id}/tags |
/api/v1/timeseries/series/tagged/{id}/tags |
|
/api/instances/{id} |
/api/v1/timeseries/instances/{id} |
|
/api/instances/{id}/get |
/api/v1/timeseries/instances/{id}/at |
Renamed |
/api/instances/{id}/latest |
/api/v1/timeseries/instances/{id}/latest |
|
/api/instances/{id}/relative |
/api/v1/timeseries/instances/{id}/relative |
|
/api/instances/{id}/absolute |
/api/v1/timeseries/instances/{id}/absolute |
|
/api/instances/tagged/{id} |
/api/v1/timeseries/instances/tagged/{id} |
|
/api/instances/tagged/{id}/get |
/api/v1/timeseries/instances/tagged/{id}/at |
Renamed |
/api/instances/tagged/{id}/latest |
/api/v1/timeseries/instances/tagged/{id}/latest |
|
/api/instances/tagged/{id}/relative |
/api/v1/timeseries/instances/tagged/{id}/relative |
|
/api/instances/tagged/{id}/absolute |
/api/v1/timeseries/instances/tagged/{id}/absolute |
|
/api/instances/tagged/{id}/tags |
/api/v1/timeseries/instances/tagged/{id}/tags |
|
/api/events |
/api/v1/timeseries/events |
Event API (server-sent events) |
/api/areas |
/api/v1/timeseries/curve-attributes/areas |
Renamed |
/api/categories |
/api/v1/timeseries/curve-attributes/categories |
Renamed |
/api/commodities |
/api/v1/timeseries/curve-attributes/commodities |
Renamed |
/api/curve_states |
/api/v1/timeseries/curve-attributes/curve-states |
Renamed — hyphen, not underscore |
/api/curve_types |
/api/v1/timeseries/curve-attributes/curve-types |
Renamed — hyphen, not underscore |
/api/data_types |
/api/v1/timeseries/curve-attributes/data-types |
Renamed — hyphen, not underscore |
/api/filters |
/api/v1/timeseries/curve-attributes/filters |
Renamed |
/api/frequencies |
/api/v1/timeseries/curve-attributes/frequencies |
Renamed |
/api/functions |
/api/v1/timeseries/curve-attributes/functions |
Renamed |
/api/scenarios |
/api/v1/timeseries/curve-attributes/scenarios |
Renamed |
/api/sources |
/api/v1/timeseries/curve-attributes/sources |
Renamed |
/api/stations |
/api/v1/timeseries/curve-attributes/stations |
Renamed |
/api/time_zones |
/api/v1/timeseries/curve-attributes/time-zones |
Renamed — hyphen, not underscore |
/api/units |
/api/v1/timeseries/curve-attributes/units |
Renamed |
/api/versions |
/api/v1/timeseries/curve-attributes/versions |
Renamed |
Authentication does not change
Section titled “Authentication does not change”- Token endpoint:
POST https://auth.volueinsight.com/oauth2/token - Grant type:
client_credentials, same scopes and parameters - Send the token as today:
Authorization: Bearer <token> - Keep your current client ID and secret
New credentials and a new auth URL will be announced separately, later.
Check that it works
Section titled “Check that it works”TOKEN=$(curl -s -u "$CLIENT_ID:$CLIENT_SECRET" -d grant_type=client_credentials \ https://auth.volueinsight.com/oauth2/token | python3 -c 'import sys,json;print(json.load(sys.stdin)["access_token"])')
curl -sS -o /dev/null -w '%{http_code}\n' -H "Authorization: Bearer $TOKEN" \ https://data-forecasts.volue.com/api/v1/timeseries/curve-attributes/areas200 means network, encryption (TLS) and authentication all work. See also
Check your connection.
What /api/v1 promises you
Section titled “What /api/v1 promises you”One version number covers the whole API. When we publish a new version, we support the
previous one for at least 12 months. Within /api/v1 we may add fields, enum values,
endpoints and optional parameters, so ignore what you do not recognise. See
API versioning for the full list.
Frequently asked questions
Section titled “Frequently asked questions”Can I change the paths and the host in separate steps?
Section titled “Can I change the paths and the host in separate steps?”Yes. During the transition the old addresses also understand the new paths. Finish on
data-forecasts.volue.com before we stop supporting the old addresses, see the timeline.
Do the old paths work on the new host?
Section titled “Do the old paths work on the new host?”No. data-forecasts.volue.com only serves the /api/v1/timeseries/... paths.
What happens if I leave out the version?
Section titled “What happens if I leave out the version?”A path without it, such as /api/series/12345 on data-forecasts.volue.com, returns
404 Not Found.
Does the Event API change?
Section titled “Does the Event API change?”Only its address: /api/v1/timeseries/events.
We use auth.wattsight.com for tokens.
Section titled “We use auth.wattsight.com for tokens.”It works the same as auth.volueinsight.com, but we stop supporting it together with the old
addresses, see the timeline. Switch to auth.volueinsight.com.
What does our network team need?
Section titled “What does our network team need?”Send them Migration: network and security teams.