Skip to content
Documentation

Migration: network and security teams

The Volue Data & Forecasts Timeseries API is moving to a new hostname, data-forecasts.volue.com. We stop supporting the old hostnames, api.volueinsight.com and api.wattsight.com, on the date in the timeline.

This page is for whoever runs your firewall, proxy or security policy. Developers changing code should read Migration: calling the API directly.

All connections are opened from your network (outbound). Responses, including the Event API stream, come back on those same connections, which a stateful firewall allows without extra rules. No inbound rules are needed: we never open connections to your network.

Purpose FQDN IP addresses Port Protocol TLS Status
Timeseries API and Event API data-forecasts.volue.com Not published, use FQDN 443/TCP HTTPS 1.2 or 1.3 New: add
Data & Forecasts web app (note) app.data-forecasts.volue.com Not published, use FQDN 443/TCP HTTPS 1.2 or 1.3 New: add
Authentication (OAuth 2.0 token) auth.volueinsight.com Not published, use FQDN 443/TCP HTTPS 1.2 or 1.3 Unchanged: keep
Authentication, alternative host auth.wattsight.com Not published, use FQDN 443/TCP HTTPS 1.2 or 1.3 Works like auth.volueinsight.com; support ends, see the timeline
Timeseries API, old addresses api.volueinsight.com, api.wattsight.com No planned change before support ends 443/TCP HTTPS 1.2 or 1.3 Remove after migration; support ends, see the timeline
Certificate revocation check (only if your clients or proxy check revocation) *.lencr.org Not published, use FQDN 80/TCP HTTP — Optional. Not needed for our Python library

No other hostnames are needed for authentication or data retrieval. Port 80 is not used for the API and is closed on data-forecasts.volue.com; the only port 80 traffic is the optional revocation check in the last row. That row depends on our certificate authority, Let’s Encrypt; if we change it, we will update this page. IPv4 only: there is no IPv6 address (AAAA record). Customers who install our Python library also need access to pypi.org and files.pythonhosted.org, or to your internal package mirror.

IP-based allowlisting is not supported. We do not publish or guarantee the IP addresses or CIDR ranges behind these hostnames; they may change without notice. Allow traffic by FQDN instead, using a proxy or firewall that supports FQDN rules or SNI-based rules (SNI, Server Name Indication, is the hostname a client sends when it opens a TLS connection).

We do not plan to change the IP addresses of api.volueinsight.com and api.wattsight.com before we stop supporting them, so existing rules for them can stay as they are during the transition.

  • Resolve the hostnames through normal DNS at connection time and respect the record TTL (time to live, how long a lookup may be cached): 3600 seconds.
  • data-forecasts.volue.com, app.data-forecasts.volue.com and auth.volueinsight.com are plain address (A) records: no CNAME chain to other hostnames, and no HTTP redirect to another host.
  • Do not pin resolved addresses in hosts files or static firewall objects.
  • The API and authentication are run separately, so their addresses can change independently. Allow each by name.

If your firewall can only filter by IP address

Section titled “If your firewall can only filter by IP address”

Route the traffic through an explicit HTTPS forward proxy that can allow by hostname.

  • The proxy must allow CONNECT to the hostnames above on port 443.
  • Our Python library uses Python requests and picks up the standard proxy environment variables for authentication, data and Event API calls. Other HTTP clients generally support the same variables or their own proxy setting.
  • From version 3.0.0, the Python library also accepts a preconfigured requests.Session (requests_session=). Developers can set the proxy and CA bundle on that session in code, instead of with environment variables. All requests, authentication included, go through it. See Your own requests session in the Python library docs.
Terminal window
export HTTPS_PROXY=http://proxy.example.com:8080
export NO_PROXY=localhost,.internal.example.com

If the proxy inspects TLS and re-signs traffic with your own certificate authority (CA), point Python at your CA bundle, either with the variable below or on the preconfigured session. Python requests uses its own CA list, not the operating system’s:

Terminal window
export REQUESTS_CA_BUNDLE=/path/to/your-ca-bundle.pem
  • data-forecasts.volue.com uses a publicly trusted certificate from Let’s Encrypt. Up-to-date clients need no action.
  • The certificate is renewed every 60–90 days. Do not pin certificates or public keys: they change at every renewal.
  • TLS 1.2 or 1.3 is required. TLS 1.0 and 1.1 are not accepted.

Not for the new hostname. Its IP addresses are not published or guaranteed. Use FQDN rules, or an explicit proxy as described above.

Do we need a wildcard such as *.volueinsight.com?

Section titled “Do we need a wildcard such as *.volueinsight.com?”

No. Allow the named hostnames in the table.

Our proxy inspects TLS. What do developers need to set?

Section titled “Our proxy inspects TLS. What do developers need to set?”

For Python, REQUESTS_CA_BUNDLE pointing at your CA bundle, or a preconfigured requests.Session with the CA bundle set, passed to the library as requests_session (see Your own requests session). Other clients need your CA in their trust store.

Our network blocks certificate revocation checks.

Section titled “Our network blocks certificate revocation checks.”

Our certificate is issued by Let’s Encrypt, which publishes revocation lists (CRL, certificate revocation list) over plain HTTP. If your clients or proxy check revocation, allow outbound HTTP on port 80 to *.lencr.org — see the optional row in the table. Python clients, including our library, do not check revocation by default; Windows-based clients and some proxies do.

Do OAuth scopes, token requests or headers change?

Section titled “Do OAuth scopes, token requests or headers change?”

No.

Not for this move. New credentials and a new auth URL will be announced separately, later.

Once the new hostname is available (see the timeline), ask a developer to run the check in Check your connection. A 200 response means network, TLS and authentication all work.

© 2026 Volue.Version v0.6.38017 November 2026