Production Environment
The production environment is designed for seamless integration into your live application, ensuring smooth and reliable operation of Veritus Agent voice AI workflows. This environment should only be used in production, where real customer interactions take place. All calls, transcripts, and webhooks in the production environment are live and will be processed by Veritus Agent’s production API.Sandbox Environment
The sandbox environment is specifically created to cater to developers’ needs. It allows you to place test calls, experiment with different scenarios, and perform comprehensive quality assurance checks. The sandbox environment is ideal for developers to ensure the functionality and compatibility of their systems before going live. While sandbox calls use the same AI and telephony stack as production, they are processed against a separate environment and should only be used for development and QA.It’s important to note that the production and sandbox environments have
separate infrastructures. This ensures that resources such as buyers and
payment services are not shared between the two environments, guaranteeing
data isolation and security.
| Environment | URL |
|---|---|
| Production | https://www.veritusagent.ai/api/v1 |
| Sandbox | https://sandbox.veritusagent.ai/api/v1 |
Benefits of environments in Veritus Agent
By using distinct hostnames for each environment, Veritus Agent ensures clear separation between production and sandbox, enabling you to manage live customer interactions and testing activities effectively. Environments play a crucial role in the integration process for several reasons. They provide distinct spaces for different purposes, allowing developers, testers, and operators to work efficiently while maintaining the integrity of live systems. Here’s why environments are important:Development and Testing
During development, engineers need to validate integrations, experiment with different scenarios, and confirm that calls, transcripts, and webhooks behave as expected. The sandbox environment provides a safe space to place real calls and run through test workflows without impacting live customer accounts. This separation prevents test activity from being mixed with production data, making it easier to iterate and troubleshoot effectively.Quality Assurance (QA) and Validation
To ensure the reliability and stability of your integration, comprehensive QA is essential. In the sandbox, you can run real calls with test data, simulate conversation flows and error paths, and validate webhook delivery under different conditions — without impacting production traffic. This controlled space helps you identify and resolve issues before deploying to production.Data Isolation and Security
Distinct environments provide data isolation and enhance security. By keeping production and sandbox traffic separate, you ensure that sensitive customer data is never exposed during development or QA. Sandbox calls can use test accounts or non-sensitive data, while production is reserved strictly for live borrower information.Efficiency and Workflow
Having dedicated environments streamlines development and testing. Developers can confidently build and debug integrations in sandbox, while operations teams know production only contains validated, live interactions. This clear separation ensures smoother collaboration and reduces risk during deployment.Sandbox vs. Production
- Sandbox Environment: Used for development, testing, and QA. Real calls are placed, but tied to test accounts and controlled data. Actions such as initiating a call or handling a webhook are processed through the sandbox API and remain isolated from production systems.
- Production Environment: Used for live, real-world interactions. When connected to the production API, all calls, transcripts, and webhooks are tied to your production account and represent actual customer activity.