SANDBOX
Build where experimentation does not touch live operations.
Hamiltonn’s non-production integration model gives developers a separate environment for supported API and workflow testing before production credentials and live customer data are involved.
Hamiltonn Cloud
Build where experimentation does not touch live operations.
The Hamiltonn sandbox is a non-production development environment used to exercise supported integration patterns without operating on live customer workloads.
Definition
What does this mean?
The Hamiltonn sandbox is a non-production development environment used to exercise supported integration patterns without operating on live customer workloads.
Hamiltonn Cloud combines reusable software infrastructure, configurable product capabilities and flexible deployment so organisations can build around their own brand and operating model.
SEPARATION
Development and production are different contexts.
Separate credentials
Keep development credentials distinct from live access.
Test data
Use non-production records appropriate to the product.
Integration development
Build API, webhook and workflow logic away from live operations.
Failure testing
Exercise error handling and retry paths safely.
WHAT TO TEST
Validate more than the happy path.
- Authentication failures and revoked credentials.
- Validation errors and missing fields.
- Pagination and larger result sets.
- Webhook duplicates and retries.
- Idempotent retry behaviour.
- Permission and tenant boundaries.
READINESS
Move to production only after the boundary is understood.
Build
Implement the integration.
Validate
Test successful and failed requests.
Observe
Add logs and operational visibility.
Secure
Protect credentials and verify permissions.
Review
Complete product-specific readiness.
Promote
Provision appropriate live access.
DOCUMENTATION
Keep environment differences explicit.
Endpoints, credentials, test data and third-party provider behaviour can differ between non-production and live environments.
FAQs
SANDBOX FAQs
Does sandbox data affect production?
No. The purpose is to keep integration development separate from live workloads.
Should production credentials be used in sandbox?
No. Development and production should use separate credentials.
Do third-party providers behave identically in test?
Not necessarily. Provider simulations and test environments can differ.
What should I test before production?
Authentication, permissions, validation, retries, idempotency, webhooks, errors and logging.
How do I request sandbox access?
Use the demo/contact process and select API Infrastructure or the relevant product.
Build on Hamiltonn Cloud.
Choose the product, modules and deployment model that fit your business, then bring the customer experience under your own brand.