Official SDKs
Go
github.com/ZeamMoney/zeam-sdk-go — backend services, CLIs, and server-to-server integrations.TypeScript
@zeammoney/sdk — Node.js, Deno, and Bun. Server-side only.Flutter
zeam_sdk on pub.dev — mobile, desktop, web, and Dart CLI.MCP server
Model Context Protocol server for AI-assisted integration from any MCP-compatible tool.
What every SDK handles
| Capability | Description |
|---|---|
| Authentication | Ed25519 challenge signing, OTP flows, OAuth pass-through, automatic token refresh |
| Track isolation | Business and Connect tokens are type-separated; the SDK refuses cross-track calls |
| Error classification | Typed errors with Kind matching (auth, validation, transient, conflict) |
| Security | Secrets are never logged, spanned, or written to disk. TLS 1.3 enforced. Constant-time webhook HMAC verification. |
| Observability | X-Request-Id propagation, OpenTelemetry hooks, structured events |
| Recipes | Pre-built workflows: OTP login, Ed25519 login, application registration, connect payment (9-step off-ramp), credential rotation |
| Version parity | Runtime handshake against /healthz ensures the SDK and gateway are compatible |
Choosing an SDK
| Use case | Recommended |
|---|---|
| Backend service, CLI, or operator tool | Go SDK |
| Node.js API server, serverless function, or Bun worker | TypeScript SDK |
| Flutter mobile or desktop app, Dart server | Flutter SDK |
| AI-assisted exploration, prototyping, or agentic workflows | MCP server |
All three SDKs expose the same recipes, the same authentication flows, and the same error types. Choose the one that matches your runtime.
No SDK for your language?
The REST API is stable and fully documented. Any HTTP client that can send JSON, setAuthorization: Bearer headers, and read HTTP status codes can integrate with Zeam directly.
Start with the API reference and the OpenAPI spec.