Turris exposes two environments to customers:
| Environment | Purpose |
|---|
| Sandbox | Testing and development |
| Production | Live operations |
Turris strongly recommends testing and building your integration with this API in the sandbox environment first.
Environment Comparison
The sandbox environment allows you to experiment with the API without incurring any charges. The following should be taken into consideration:
| Aspect | Sandbox | Production |
|---|
| Features | Full feature parity | Full features |
| Cost | Free | Chargeable per subscription |
| Data | Test data only | Real data |
| NPN Data | Limited/scrambled | Full NIPR data |
| Credentials | Sandbox-specific | Production-specific |
Important Considerations
Never use third-party email addresses in the sandbox environment.Turris recommends using only emails you have full access to. This is particularly important when inviting or adding agencies and agents. Any downstream entity invited to onboard with an upstream entity will be sent an invitation email with a magic link.
NPN Availability
Not all NPN numbers exist in the sandbox environment. If they do exist, their associated compliance data is most likely scrambled or incorrect.
Credential Isolation
- API Client credentials are environment-specific
- Restricted Access Tokens are environment-specific
- Credentials are not portable between environments
Data Isolation
The sandbox and production environments are entirely separate. Data is not portable between them.
Base URLs
| Environment | Base URL |
|---|
| Production | https://public.api.live.turrisfi.com |
| Sandbox | https://public.api.sandbox.turrisfi.com |