Environments
Test and Integrate easily with Aiprise applications
AiPrise provides two isolated environments - Sandbox and Production - so you can develop, test, and deploy verification workflows with confidence. Each environment has its own data, API keys, templates, and rate limits, ensuring clean separation between testing and live operations.
Sandbox Environment
The Sandbox environment is designed for development, integration testing, and internal training. It mirrors AiPrise’s Production behaviour while returning test-safe data and mock responses when required.
Base URL: https://api-sandbox.aiprise.com/api/v1/
Use Sandbox to:
- Build and validate your API or SDK integration
- Test verification workflows end-to-end without any charges
- Simulate edge cases, document issues, biometric mismatches, or AML hits
- Train compliance teams and operators using safe test profiles
- Verify webhooks, callback handling, and session lifecycle logic
Key characteristics:
- Complete isolation from Production (data does not carry over)
- Uses mock or simulated provider responses for some checks
- No billing for Sandbox activity
- Requires separate Sandbox API keys
Sandbox is the recommended place to iterate on templates, workflows, and callback logic before switching to Production.
Production Environment
The Production environment is where all live KYC and KYB verifications run. It connects to real data sources, returns authoritative results, and is tied to your billing plan.
Base URL: https://api.aiprise.com/api/v1/
Use Production for:
- Verifying real customers and businesses
- Running compliance-required checks such as AML, liveness, registry lookups
- Operational monitoring and case management
Key characteristics:
- Real verification results and government/registry data
- Billable usage according to your pricing plan
- Higher throttle limits and guaranteed SLAs
- Secure, hardened infrastructure for live traffic
Environment Isolation
To keep your integration safe and predictable:
- Sandbox and Production have separate databases
- API keys are not interchangeable
- Templates, workflows, and profiles must be created separately per environment
- Webhooks must be configured per environment
- Issues in one environment do not affect the other
Promoting to Production:
- Test your integration thoroughly in Sandbox
- Generate a Production API key
- Update your base URL and credentials in your application
- Validate Production webhook delivery
- Start onboarding real users and businesses
Updated about 7 hours ago