Environments
SlaunchX provides two distinct environments for API integration: Sandbox for development and testing, and Production for live operations. Both environments expose the same API surface and authentication mechanism, but they are fully isolated -- data, API keys, and configurations do not cross environment boundaries.
Environment URLs
| Sandbox | Production | |
|---|---|---|
| API Base URL | https://sandbox. | https:// |
| Dashboard | https://sandbox.dashboard.slaunchx.cc | https://dashboard.slaunchx.cc |
| Purpose | Development, testing, QA | Live transactions, real funds |
| Data | Simulated, resettable | Persistent, real |
Start with Sandbox
Always build and test your integration in the Sandbox environment first. Switch to Production only after you have validated your implementation end-to-end.
Authentication
Both environments use the same HMAC-SHA256 authentication mechanism. However, API keys are environment-specific -- a Sandbox API key will not work in Production, and vice versa.
| Item | Sandbox | Production |
|---|---|---|
| API Key prefix | sk_test_ | sk_live_ |
| API Secret | Unique per environment | Unique per environment |
| Auth mechanism | HMAC-SHA256 | HMAC-SHA256 |
You can generate and manage API keys for each environment independently from the respective dashboard.
Sandbox Features
The Sandbox environment is designed for safe, risk-free development:
- Simulated transactions -- All transfers and wallet operations are simulated. No real money is moved.
- Test data -- Pre-populated test wallets and accounts are available for immediate use.
- Instant processing -- Transactions that may take time in Production are processed instantly in Sandbox.
- Resettable state -- Sandbox data can be reset from the dashboard without affecting Production.
- Full API coverage -- Every Production endpoint is available in Sandbox with identical request/response formats.
Test Credentials
Obtaining Sandbox API Keys
- Log in to the Sandbox Dashboard.
- Navigate to Settings > API Keys.
- Click Create API Key and assign the desired scopes.
- Copy both the API key (
sk_test_...) and the API secret. The secret is only shown once.
Test Wallets
Sandbox environments come with pre-provisioned test wallets. You can also create additional wallets via the API or dashboard. All Sandbox wallets start with a configurable test balance.
Test Card Numbers / Wallet Addresses
If your integration involves external payment methods, the following test values are available in Sandbox:
| Type | Value | Behavior |
|---|---|---|
| Test wallet (success) | Pre-provisioned w_test_* wallets | Transactions succeed normally |
| Test wallet (insufficient funds) | Wallet with zero balance | Returns W3001 (INSUFFICIENT_BALANCE) |
| Test wallet (frozen) | Frozen test wallet | Returns W1003 (ACCOUNT_FROZEN) |
Differences from Production
While the Sandbox mirrors Production as closely as possible, some differences apply:
| Aspect | Sandbox | Production |
|---|---|---|
| Rate limits | More permissive | Standard rate limits apply |
| Data persistence | Data may be reset periodically | Fully persistent |
| Webhooks | Delivered to your configured endpoint, same format | Same |
| Transaction processing | Instant, simulated | Real processing times |
| Monitoring & alerts | Limited | Full operational monitoring |
:::caution Sandbox data is not permanent Sandbox data may be reset during maintenance windows. Do not rely on Sandbox data for long-term storage or record-keeping. :::
Going Live Checklist
Before switching your integration from Sandbox to Production, complete the following steps:
Replace API keys -- Swap your
sk_test_credentials forsk_live_Production credentials. Never hardcode keys; use environment variables or a secrets manager.Update base URL -- Change your API base URL from
https://sandbox.tohttps://.Verify webhook endpoints -- Ensure your Production webhook receiver is deployed, publicly accessible, and configured in the Production dashboard.
Test with small real transactions -- Run a few low-value transactions to confirm end-to-end correctness before processing at scale.
Enable production monitoring -- Set up alerting for API errors (
5xxresponses), latency spikes, and webhook delivery failures.Review IP whitelist -- If you use IP whitelisting, ensure your Production server IPs are added to the Production API key configuration.
Confirm idempotency handling -- Verify that your retry logic uses idempotency keys to prevent duplicate transactions in Production.
Code Example
An environment-aware client setup that switches between Sandbox and Production based on configuration:
Next Steps
- API Integration Overview -- How the SlaunchX API works and what you need to get started.
- HMAC Authentication -- Step-by-step guide to signing API requests.
- Error Handling -- Response envelope format and error code catalog.