Before moving to production, confirm your integration uses production keys, production base URLs, safe retries, and documented wallet flows.Documentation Index
Fetch the complete documentation index at: https://stabyl.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Checklist
| Area | Requirement |
|---|---|
| Authentication | API keys are stored server-side and rotated through an approved process |
| Orders | Create, cancel, and replace calls send Idempotency-Key |
| Wallets | Chain availability is read from GET /partner/wallets/chains |
| Deposits | Crypto routes and fiat deposit accounts are shown exactly as returned |
| Errors | 400, 401, 403, 404, 409, and 429 responses are handled |
| Simulation | Simulation calls are removed from production workflows |
Required Headers
UseX-Api-Key on authenticated endpoints and Content-Type: application/json on JSON writes. Use Idempotency-Key on order writes.
Common launch blockers include incomplete KYB, unsupported chain assumptions, or retry logic that changes idempotency keys.
Production Verification
Before enabling automation against production funds:- Run a full staging order lifecycle: create, read, cancel, replace, and reconcile.
- Run a staging deposit test for every chain you plan to display.
- Confirm your reconciliation job can resume after downtime without duplicating records.
- Confirm alerts exist for repeated
401,403,409,429, and5xxresponses. - Confirm API keys are not present in frontend code, mobile apps, analytics tools, or browser logs. |