SDK Overview
Official Spare client libraries, or REST integration where SDKs aren't yet available.
Spare's official SDKs let you integrate without hand-crafting HTTP requests, token refresh, or serialization.
Available now
- The React Native SDK (
@spare-technologies/spare-link) is published on npm (v1.0.0). It runs the Spare Link payment flow in iOS and Android apps for the UAE. See the React Native SDK guide to integrate. - The Flutter SDK (
spare_link) is published on pub.dev (v1.0.0). It runs the same Spare Link payment flow in Flutter iOS and Android apps for the UAE. See the Flutter SDK guide to integrate. - The TypeScript SDK is published on npm as
@spare-technologies/spare-api(v1.0.0).
Other SDKs coming soon
The Python, Java, C#, and Go SDKs below are under review and not yet published; until they ship, integrate over the REST API, where every endpoint has schemas, examples, and an in-browser Try-it.
SDK Coverage
| SDK | Package | Status |
|---|---|---|
| React Native (UI) | @spare-technologies/spare-link on npm | Available (v1.0.0, UAE) |
| Flutter (UI) | spare_link on pub.dev | Available (v1.0.0, UAE) |
| TypeScript / Node | @spare-technologies/spare-api on npm | Available (v1.0.0, UAE) |
| Python | spare-api on PyPI | Under review |
| Java | com.spare:spare-api on Maven Central | Under review |
| C# | SpareApi on NuGet | Under review |
| Go | Go module (path published at release) | Under review |
The TypeScript, Python, Java, C#, and Go SDKs share a consistent, typed client surface and aligned models. The React Native and Flutter SDKs are mobile clients for the Spare Link payment flow.
Why use an SDK
- Automatic OAuth token exchange and refresh via
Configuration - Typed request/response models aligned with the API
- Consistent error types (
SpareApiError,SpareApiTimeoutError) - Crypto helpers for signed payloads where required
Version compatibility
SDK major versions track API contract versions. Check the release notes in each SDK repository for the supported API version matrix.