Sandbox environment
A sandbox environment is available for integration testing before production deployment. BillSentry will provide:
| Item | Details |
|---|
| Sandbox Client ID & Secret | Separate M2M credentials for the sandbox |
| Sandbox API Key | A distinct x-api-key value |
| Sandbox Endpoint URL | A non-production API gateway URL |
| Sandbox Token URL | Separate token endpoint for sandbox auth |
| Sample test scenarios | Pre-defined bill payloads covering common states and bill types |
All sandbox requests are isolated from production data. No production records are created or modified.
Transport and security requirements
- All requests must use HTTPS. HTTP is not supported.
- Minimum TLS version: 1.2
- Never include your
client_secret in client-side code, version control, or log files
- Rotate your
client_secret immediately if you believe it has been compromised — contact BillSentry support
Support
| Need | Contact |
|---|
| Request sandbox access | billsentry.com/developers |
| Integration questions | Contact your BillSentry integration engineer |
| Production incidents | Include the x-request-id from the failed response |
| Credential rotation or revocation | Contact BillSentry support immediately |
