Skip to content
Documentation

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.

  1. The host: api.volueinsight.com and api.wattsight.com become data-forecasts.volue.com.
  2. The path: insert /v1/timeseries after /api in every path.
  3. 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-02
GET https://data-forecasts.volue.com/api/v1/timeseries/series/12345?from=2026-11-01&to=2026-11-02
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

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
  • 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.

Terminal window
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/areas

200 means network, encryption (TLS) and authentication all work. See also Check your connection.

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.

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.

No. data-forecasts.volue.com only serves the /api/v1/timeseries/... paths.

A path without it, such as /api/series/12345 on data-forecasts.volue.com, returns 404 Not Found.

Only its address: /api/v1/timeseries/events.

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.

Send them Migration: network and security teams.

© 2026 Volue.Version v0.6.38017 November 2026