Network requirements
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 | Hostname (FQDN) | Port | Protocol | TLS |
|---|---|---|---|---|
| Timeseries API and Event API | data-forecasts.volue.com |
443/TCP | HTTPS | 1.2 or 1.3 |
| Data & Forecasts web app (note) | app.data-forecasts.volue.com |
443/TCP | HTTPS | 1.2 or 1.3 |
| Authentication (OAuth 2.0 token) | auth.volueinsight.com |
443/TCP | HTTPS | 1.2 or 1.3 |
| Certificate revocation check (optional) | *.lencr.org |
80/TCP | HTTP | — |
No other hostnames are needed for authentication or data. Port 80 is not used for the API.
The revocation check is only needed if your clients or proxy check certificate revocation.
To install the Python library you also need access to pypi.org and
files.pythonhosted.org, or your internal package mirror.
Allow by hostname, not IP address
Section titled “Allow by hostname, not IP address”- IP addresses are not published or guaranteed and may change without notice. Allow traffic by hostname (FQDN or SNI rules), or through an explicit HTTPS proxy.
- Resolve hostnames through normal DNS at connection time and respect the record TTL (3600 seconds). Do not pin addresses in hosts files or static firewall objects.
- IPv4 only. There is no IPv6 (AAAA) record.
Certificates and TLS
Section titled “Certificates and TLS”- Certificates are publicly trusted, from Let’s Encrypt. Up-to-date clients need no action.
- Certificates are renewed every 60–90 days. Do not pin certificates or public keys.
- TLS 1.2 or 1.3 is required.
For proxy setup, TLS inspection and more detail, see Network and security teams. To test your setup, see Check your connection.
Was this page helpful?Thanks for your feedback!