Skip to content
Documentation

FAQ

The server seems to refuse my connection. What is wrong?

Section titled “The server seems to refuse my connection. What is wrong?”

This is almost always caused by a proxy in your network that decrypts TLS traffic and replaces our certificate with its own. Your client then rejects the certificate, as it should.

The best fix is for your IT department to let the API hostnames pass through the proxy unchanged (see Network requirements). If that is not possible, get your organisation’s CA certificate bundle and configure your HTTP client to trust it. See Migration: network and security teams for the proxy and CA settings.

We see error “104” and the connection is lost.

Section titled “We see error “104” and the connection is lost.”

When we deploy a new version of the API, our servers restart and existing connections are dropped. You then see error 104 (“connection reset by peer”), which is an operating system error, not an HTTP status. Your client must open a new connection and retry.

I’m missing events, or the connection drops now and then.

Section titled “I’m missing events, or the connection drops now and then.”

Many things between you and us can drop a long-lived connection: firewalls, NAT translation tables, proxies. The server sends a heartbeat about every 15 seconds. Check the keep-alive and idle timeout settings in your network and client — if the connection drops at a consistent interval, that is most likely the cause. Implement reconnects with Last-Event-ID, see Events.

I cannot subscribe to all the curves I want.

Section titled “I cannot subscribe to all the curves I want.”

The Event API is designed for curves that are critical to follow live. Most curves are not updated often, or are not time-critical. Split your curves into two groups:

  • Time-critical curves: use the Event API.
  • The rest: poll in batch jobs at an interval that matches the curve, using modified_since. It seldom makes sense to follow monthly curves live.

The Event API also sends what look like duplicate events, from internal updates that arrive at almost the same time. By the time you receive them, the last one is applied, so you usually need to query only once.

Each event you act on leads to more requests, so many listeners quickly fan out into a lot of parallel traffic. Limits on curves per connection, or connections per customer, may change if needed to keep the API stable. We try to announce such changes in advance, but cannot guarantee it, so stay below the limits. See Best practice.

I cannot access a service, even though I should have access.

Section titled “I cannot access a service, even though I should have access.”

If our sales team has confirmed your access:

  1. Log out of the application, then log out at auth.volueinsight.com/logout, and log in again.
  2. If that does not help, clear your browser cookies for volueinsight.com and its subdomains.

If you still have problems, contact support.

Why does accessRange start at a different date than the curve’s data?

Section titled “Why does accessRange start at a different date than the curve’s data?”

accessRange is the subscription period of the sales package the curve belongs to, usually set from your contract. It does not mean the curve has data from that date. See Access range.

The API is an application in front of our databases, with a separate access control service (auth.volueinsight.com) that manages users. It runs in a contained cloud setup where nothing is exposed except the API endpoints.

  • Credentials. The main risk to you is that your usernames, passwords or OAuth client credentials are compromised. Use complex, unique passwords, and keep client secrets safe. Customer credentials have no write access, so misused credentials cannot change our systems or data.
  • Misuse. Misused credentials could be used to overload the API. If we detect this, we contact the users involved, may temporarily block them, and may require a rotation of keys.
  • Validate data. As with any web source, type-check and validate data before you feed it into your systems, especially physical control systems, so extreme values cannot cause harm.
  • Open-source client. Our Python library is open source and scanned by GitHub for vulnerabilities, so you can see exactly what it does.

We monitor the API and alert on unexpected behaviour, to respond quickly to operational issues.

© 2026 Volue.Version v0.6.38017 November 2026