Platform — Developer Tools

Environments

Every Ventryx organization has isolated live and test environments. Develop and test integrations without risk to production data, billing, or workflows.

Live vs. test

	Live	Test
API key prefix	`vtx_live_`	`vtx_test_`
Billing triggered	Yes	No
Webhooks delivered	Yes	Configurable
Data persisted	Yes	30 days max
Rate limits	Per plan	10 req/s

Switching environments

The active environment is determined by the API key you use. Pass a vtx_test_* key to interact with the test environment; pass a vtx_live_* key for production. No URL changes are needed.

Using environment variables

# Development / testing
export VENTRYX_API_KEY=vtx_test_your_test_key

# Production
export VENTRYX_API_KEY=vtx_live_your_live_key

Environment variables in the CLI

# Check current environment
vtx env status

# Explicitly switch
vtx env switch test
vtx env switch live

Environment isolation

Resources in test and live environments are fully isolated. A workflow created in the test environment does not exist in live, and vice versa. You must create and configure resources separately in each environment.

Use the CLI's vtx workflows deploy command in your CI pipeline to keep workflows synchronized between environments automatically.

Staging environments (Enterprise)

Enterprise organizations can provision additional named environments (e.g., staging, preview) for more complex deployment pipelines. Contact sales to enable this feature.