Choose an SDK

Install a pinned release for your runtime. All six SDKs have separate public repositories. Keep server keys on your backend and initialize clients with consent disabled until your consent flow grants permission.

JavaScript, React Native, and Expo

These packages currently ship as GitHub release tarballs, not npm registry releases. Install the appropriate package:

javascript

npm install https://github.com/LinkRunway/linkrunway-sdk-js/releases/download/0.2.0/linkrunway-sdk-0.2.0.tgz

react-native

npm install https://github.com/LinkRunway/linkrunway-sdk-react-native/releases/download/0.2.0/linkrunway-sdk-react-native-0.2.0.tgz

expo

npm install https://github.com/LinkRunway/linkrunway-sdk-expo/releases/download/0.2.0/linkrunway-sdk-expo-0.2.0.tgz

React Native and Expo use the JavaScript core, with native lifecycle and storage integration. Expo's config plugin is compiled in the published package; test native links in a development or release build, not only Expo Go.

iOS

Add the Swift package in Xcode using this repository URL and version:

.package(url: "https://github.com/LinkRunway/linkrunway-sdk-ios", from: "0.2.1")

Read the iOS guide for deployment targets, Universal Links, storage, and platform evidence.

Android

Add JitPack to your repositories, then the pinned dependency:

maven("https://jitpack.io")
// app module:
implementation("com.github.LinkRunway:linkrunway-sdk-android:0.2.1")

Read the Android guide for the full Gradle configuration and App Links setup.

Flutter

The package is a Git dependency, not a pub.dev release:

dependencies:
  linkrunway:
    git:
      url: https://github.com/LinkRunway/linkrunway-sdk-flutter.git
      ref: 0.1.0

Read the Flutter guide for native bridges and supported platforms.

Select an API endpoint

Use the API base URL supplied by your workspace, without a trailing /v1. Hosted integrations can use https://api.linkrunway.com. Placeholder domains in platform guides must be replaced with a host actually serving the LinkRunway API; a branded redirect-only host is insufficient.

Report business events from your backend

JavaScript can run in a server runtime with a server key. Any backend language can call the REST API. Confirm payments with your payment provider and use stable event IDs. Mobile SDKs never make a client payment event trusted.

Continue with testing, errors and retries, or releases and support.