Essentials
Concepts that apply across every Syper integration.
DraftThe Syper public API has not been released yet. Essentials describes the intended platform model.
Essentials covers the ideas you need regardless of what you build: how Syper is organised, how requests are authenticated, and how to build integrations that behave well under failure.
If you are new, start with the Quickstart.
How the documentation is organised
- Essentials
- Cross-cutting concepts: authentication, environments, permissions, webhooks, and reliability.
- Accounts
- Who operates the financial relationship — a person, a business, or an agent.
- Products
- What financial capability an account uses — payments, cards, treasury, credit, investments, savings.
- Integrations
- Where and how Syper connects — apps, AI agents, robots, devices, telecom channels, and financial rails.
- Tools
- What you build with — CLI, SDKs, MCP, sandbox, and debugging tools.
- API Reference
- Exact endpoints, fields, events, and error codes.
In this section
Core — Authentication, API Keys, Environments, Permissions, Webhooks.
Reliability — Errors, Rate Limits, Idempotency.
Last updated on