Getting started
Sandbox & Live
Two isolated environments with their own base URLs, keys, data and provider adapters.
| Property | Sandbox | Live |
|---|---|---|
| Base URL | https://api.gloresend.com/sandbox/v1 | https://api.gloresend.com/v1 |
| Key prefix | gs_test_ | gs_live_ |
| Rate limit | 120 req/min per key | 300 req/min per key |
| Money | Simulated (test_data: true) | Real — once a provider is authorized |
Isolation guarantees
- The environment is determined by the base URL. A key from the other environment is rejected with
environment_mismatch. - Transfers, balances, idempotency keys, webhook endpoints, events and logs are stored with their environment and every query filters on it.
- Sandbox transfers are handled by a simulator that makes no network calls. Live transfers can only use a Live provider adapter.
- There is no fallback: if Live is unavailable, requests fail; they are never served by the Sandbox.
Getting Live access
- The organization owner enables two-factor authentication.
- The owner requests Live access from Organization in the dashboard. The status becomes pending.
- GLORESEND reviews the request outside the product (onboarding, agreements and compliance) and approves or rejects it.
- Once approved, owners and admins with 2FA can create
gs_live_keys and Live webhook endpoints.
Current status of Live operations
No Live payment provider is integrated in this deployment. Live keys can authenticate (GET /ping, GET /currencies, GET /transfers), while balance and transfer creation requests return 503 live_operations_disabled or 503 provider_not_configured. Nothing is reserved or recorded when that happens, and the idempotency key is released.See Errors for the full list of codes.