Quick Start

Add the Stay22 Maven repository in settings.gradle.kts:

dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        maven { url = uri("https://raw.githubusercontent.com/Stay22/stay22-android-sdk/main/maven") }
    }
}

Then add the dependency:

dependencies {
    implementation("com.stay22:sdk:1.3.0")
}

In Xcode, go to File > Add Package Dependencies and enter:

https://github.com/Stay22/stay22-ios-sdk

Or add it to Package.swift:

dependencies: [
    .package(url: "https://github.com/Stay22/stay22-ios-sdk.git", from: "1.2.0")
]

Add the Stay22SDK product to your app target.

Add the package to pubspec.yaml, pinned to a release tag:

dependencies:
  stay22_flutter:
    git:
      url: https://github.com/Stay22/stay22-flutter-sdk.git
      ref: "1.3.0"

Then run flutter pub get.

The plugin bundles the iOS framework, so there is no iOS equivalent of this step. Android resolves the native SDK from Stay22's Maven repository, which your app declares once in its top-level Android build file. Depending on when your project was created that file is either Kotlin DSL or Groovy, so use the one you have.

android/build.gradle.kts

allprojects {
    repositories {
        google()
        mavenCentral()
        maven { url = uri("https://raw.githubusercontent.com/Stay22/stay22-android-sdk/main/maven") }
    }
}

android/build.gradle

allprojects {
    repositories {
        google()
        mavenCentral()
        maven { url 'https://raw.githubusercontent.com/Stay22/stay22-android-sdk/main/maven' }
    }
}

Without either one, the Android build fails with Could not find com.stay22:sdk.

The plugin supports Android and iOS. Importing it on web or desktop is safe; calling into it throws, so guard shared code with Stay22.isSupportedPlatform.

Install from GitHub. The package is not on npm.

npm install github:Stay22/stay22-capacitor-sdk#0.1.2
npx cap sync

Pin the tag you want from the Capacitor releases.

The plugin bundles the iOS framework. Android resolves com.stay22:sdk from Stay22's Maven repository, which your app declares once. The wrapped Android SDK needs API 26. A default Capacitor 6 app is API 22, so set minSdkVersion to 26 in variables.gradle.

If repositories live in android/build.gradle:

allprojects {
    repositories {
        google()
        mavenCentral()
        maven { url 'https://raw.githubusercontent.com/Stay22/stay22-android-sdk/main/maven' }
    }
}

If they live in settings.gradle (dependencyResolutionManagement) instead, add the same URL there. Templates that set FAIL_ON_PROJECT_REPOS will reject the allprojects block.

The plugin supports Android and iOS. There is no web or desktop implementation.

Call from Application.onCreate():

import android.app.Application
import com.stay22.sdk.Stay22

class MyApp : Application() {
    override fun onCreate() {
        super.onCreate()

        Stay22.isEnabled = userHasOptedInToStay22Offers
        Stay22.initialize(application = this, aid = "your-partner-id")
    }
}

Call early in your app launch:

import Stay22SDK

Stay22.isEnabled = userHasOptedInToStay22Offers
Stay22.initialize(aid: "your-partner-id")

Declare the partner ID natively, so the SDK starts during app launch rather than after Dart runs.

ios/Runner/Info.plist:

<key>Stay22PartnerAID</key>
<string>your-partner-id</string>

android/app/src/main/AndroidManifest.xml, inside <application>:

<meta-data
    android:name="com.stay22.sdk.PartnerAID"
    android:value="your-partner-id" />

This is the recommended setup on both platforms, for a different reason on each. On iOS it is the only arrangement that reliably opens the booking page for a notification tapped from a cold start — Dart runs after iOS has already decided who receives that tap. On Android it is what lets the notification permission prompt find a live screen to appear on.

Declaring the ID natively starts the SDK before any Dart runs, which has one consequence worth planning for: on a first launch the startup request goes out before a Dart await Stay22.setEnabled(false) can land. Later launches honour the stored value.

So pick the arrangement that matches your consent model:

• Stay22 may run by default. Declare the ID natively, and set the gate from Dart whenever the user changes it. You keep the cold-start notification tap.
• Stay22 must not be contacted before the user consents. Skip the native declaration and initialize from Dart once they have. On iOS this gives up the cold-start tap.

import 'package:stay22_flutter/stay22_flutter.dart';

await Stay22.setEnabled(userHasOptedInToStay22Offers);

// Only when you are not declaring the ID natively.
await Stay22.initialize(aid: 'your-partner-id');

Every call returns a Future and reports failures as a PlatformException. Calls that need a live SDK fail with the not_initialized error code if they run before initialization finishes.

Declare the partner ID natively, so the SDK starts while Capacitor sets up its bridge, before any of your JavaScript runs.

ios/App/App/Info.plist:

<key>Stay22PartnerAID</key>
<string>your-partner-id</string>

android/app/src/main/AndroidManifest.xml, inside <application>:

<meta-data
    android:name="com.stay22.sdk.PartnerAID"
    android:value="your-partner-id" />

This is the recommended setup on both platforms. On iOS it is the only arrangement that reliably opens the booking page for a notification tapped from a cold start. On Android, Stay22.initialize({ aid }) from JavaScript can miss the first Activity resume, so the permission prompt may find no live screen.

Declaring the ID natively starts the SDK before JavaScript runs, which has one consequence worth planning for: on a first launch the startup request goes out before await Stay22.setEnabled({ enabled: false }) can land. Later launches honour the stored value. The enabled flag defaults to true until you set it.

So pick the arrangement that matches your consent model:

• Stay22 may run by default. Declare the ID natively, and set the gate from JavaScript whenever the user changes it. You keep the cold-start notification tap.
• Stay22 must not be contacted before the user consents. Skip the native declaration and initialize from JavaScript once they have. On iOS this gives up the cold-start tap.

import { Stay22 } from '@stay22/capacitor';

await Stay22.setEnabled({ enabled: userHasOptedInToStay22Offers });

// Only when you are not declaring the ID natively.
await Stay22.initialize({ aid: 'your-partner-id' });

Calls that need a live SDK reject with not_initialized if they run before initialization finishes.

Stay22.requestNotificationPermission()

Handles the Android 13+ runtime permission; on older versions it's a no-op. Check the current state anytime with Stay22.hasNotificationPermission().

Task {
    await Stay22.requestNotificationPermission()
}

Prompts for local notification permission. Check the current state anytime with await Stay22.hasNotificationPermission().

final granted = await Stay22.requestNotificationPermission();

Prompts where the system allows one, and returns the user's answer. On Android 12 and below, once the user has already denied, or when the notification channel is off, it returns the current state without prompting. Check the current state anytime with await Stay22.hasNotificationPermission().

const { value: granted } = await Stay22.requestNotificationPermission();

Shows the system prompt and reports what the user chose. Resolves with the current state when no prompt can be shown. Check the current state anytime with await Stay22.hasNotificationPermission().

await Stay22.setTravelContext(
  TravelContext(
    address: 'Paris, France',
    checkinDate: '2026-03-20',
    checkoutDate: '2026-03-25',
  ),
);

Invalid input throws an ArgumentError before anything reaches the platform channel.