Introduction
The Superbank API is organized around REST. It accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes and verbs.Base URLs
All endpoints are versioned with
/v0/ prefix.OpenAPI specification
The complete OpenAPI 3.0 specification is published alongside this documentation:Download OpenAPI 3.0 spec
Feed it into
openapi-generator (or any compatible tool) to
generate a typed client in TypeScript, Go, Python, or any other supported language. The file is
regenerated on every release.Authentication
All API requests require an API key passed in theX-Api-Key header:
Rate Limits
When you exceed the rate limit, you’ll receive a
429 Too Many Requests response.
Endpoints
Settlement Requests
Payments
Webhooks
Response Format
All responses are returned in JSON format withsnake_case field names:
Errors
Error responses include a status code and message:Reliability
Superbank is designed to make integrations resilient by default.- Webhooks for state changes. Subscribe an endpoint to be notified the moment a settlement, payment, or pool changes state — see the Webhooks guide. Polling is supported as a fallback but webhooks have lower latency and don’t burn rate-limit budget.
- Lifecycle reference. The Real-Time On-Ramping guide walks the full settlement lifecycle and shows where webhook events fit between status transitions.