Sandbox environment
The sandbox exposes the same API endpoints as production with identical request/response formats. Your integration code should work in both environments with only a base URL and API key change.
Getting sandbox access
Sandbox credentials are issued during Stage 3 (Technical integration) of onboarding:- Sandbox API key — Separate from your production key; no rotation required during testing
Test scenarios
Use the scenarios below for edge-case testing. Conditions you cannot trigger yourself — such as a halted or restricted corridor — can be arranged with the Ratio team.Normal operation
Normal operation
Default state. All corridors active, oracle feeds fresh, pools healthy. Use this for happy-path testing — verifying the full quote → execute → settle → confirm flow for each corridor you intend to support.
State transitions
State transitions
Test how your integration handles protective states and trading halts (arranged with the Ratio team). Verify that your UI degrades gracefully when corridors are paused or the system enters a protective state.
Oracle failures
Oracle failures
Quoting returns HTTP
503 when prices are stale or sources diverge. Verify that your error handling correctly processes HTTP 503 responses from the quote endpoints, checks corridor state via GET /v1/corridors, and presents appropriate messaging to downstream users.Quote expiry
Quote expiry
Request a firm quote and wait for it to expire before submitting the transaction on-chain. Verify that your flow handles the rejected (reverted) transaction and re-requests a fresh firm quote without requiring manual intervention.
Volume limits
Volume limits
Submit transactions that exceed configured daily volume limits. Verify that rejections are handled gracefully and that your system does not retry automatically in a way that could cause duplicate submissions.