SDKs
Linkit clients, supported runtimes, API coverage and direct downloads.
SDKs
Choose the client for your application's runtime. Each SDK has a generated public API service covering the same 136 published operations, with typed helpers for common flows. Public names and signatures remain compatible with the existing clients.
| Client | Runtime |
|---|---|
| C# / .NET 10 | .NET 10 |
| C# / .NET Framework 4.8 | .NET Framework 4.8 |
| TypeScript | Node.js 18 or later, or a runtime with fetch |
| Python | Python 3.11 or later |
| Rust | Rust 1.85 or later |
| Dart / Flutter | Dart 3.3 or later |
| Kotlin / JVM | JVM 17 or later |
| Swift | Swift 6; macOS 14, iOS 17, watchOS 10, tvOS 17, or Linux |
| C++ | C++20 |
| Zig | Zig 0.16.0 |
Download the SDKs. Each download contains assemblies or source files to reference from your application.
Integration sequence
Configure the server origin and bearer token. Reuse the client and its connections. Create branches and products before dependent SKUs. Keep record IDs separate from your external references. Use canonical Orders reads when vendor status names or fractional quantities matter.
For changes, process each page and then persist its cursor. Verify webhook signatures against the original request bytes. Confirm an uncertain POST or PATCH before repeating it; the SDKs do not automatically replay those methods.
Trial and grace accounts can create branches under the dashboard's exemptions. Afterward, successfully inserted branches debit their activation fee. An insufficient wallet returns a clear error with the required and available amounts.