Skip to content

Deployment modes and the API base URL

Which base URL an Venturi API call uses depends on how Venturi is deployed for you. There are two deployment modes, and getting the base URL right is the first thing to settle before following any other API page.

The base-URL rule

The base URL is not always https://api.venturi.systems.

  • SaaS tier (Venturi-hosted): the tenant API base URL is https://api.venturi.systems.
  • Self-hosted (Venturi in your own cloud): the base URL is your own instance, for example https://<your-venturi-instance> — the host your onboarding contact gives you.

api.venturi.systems is the SaaS-tier host only. If you run Venturi self-hosted, do not point at api.venturi.systems; point at your own instance.

The two modes

SaaS tier (Venturi-hosted) Self-hosted
Where Venturi runs Venturi's cloud A dedicated data plane inside your own cloud trust boundary
Tenant API base URL https://api.venturi.systems https://<your-venturi-instance> (your host)
Who provides the host Standard, shared host Your onboarding contact provides the exact host
Data residency Venturi-operated, residency-scoped Stays entirely within your environment

In both modes the paths are identical — the public API lives under /api/v1 and partner integrations under /api/partner/v1. Only the host differs. Every example in the REST API and across the developer docs is relative to whichever base URL applies to your deployment mode.

Reading the API examples

The developer docs are written with the self-hosted placeholder https://<your-venturi-instance> so they are correct for self-hosted readers by construction. If you are on the SaaS tier, substitute https://api.venturi.systems for that placeholder:

curl https://<your-venturi-instance>/api/v1/attribution?limit=5 \
  -H "Authorization: Bearer $ARGMIN_TOKEN"

curl https://api.venturi.systems/api/v1/attribution?limit=5 \
  -H "Authorization: Bearer $ARGMIN_TOKEN"

Both calls hit the same paths and return the same shapes; only the host changes.

The control plane is separate

There is one host on api.venturi.systems that is not a tenant API: api.venturi.systems/control/v1/... is the control plane, which serves signed, public, customer-data-free artifacts such as the energy catalog that feeds the public AI Energy Index. The control plane carries no customer data and is distinct from the tenant API in path root, authentication, and cache policy. Do not confuse the control-plane host with your tenant API base URL — your tenant API base URL is determined solely by your deployment mode, as above.

Where to go next