• Getting Started
  • What is Stytch?
  • Why should I use the Stytch SDK?
  • What can I do with the Stytch SDK?
    • Consumer Applications
    • B2B Applications
    • Async Options
  • How do I start using Stytch?
• Requirements
• Installation and setup
  • Consumer Applications
  • B2B Applications
• Usage
  • Deeplink Handling
  • Example app
  • Authenticating
• Documentation
• FAQ
• Questions?
• License

Stytch is an authentication platform, written by developers for developers, with a focus on improving security and user experience via passwordless authentication. Stytch offers direct API integrations, language-specific libraries, and SDKs (like this one) to make the process of setting up an authentication flow for your app as easy as possible.

Stytch's SDKs make it simple to seamlessly onboard, authenticate, and engage users. The Android SDK provides the easiest way for you to use Stytch on Android. With just a few lines of code, you can easily authenticate your users and get back to focusing on the core of your product.

There are a number of authentication products currently supported by the SDK, with additional functionality coming in the near future! The full list of currently supported products is as follows:

• Magic links
  • Send/authenticate magic links via Email
• OTPs
  • Send/authenticate one-time passcodes via SMS, WhatsApp, Email
• Passwords
  • Create or authenticate a user
  • Check password strength
  • Reset a password
• Sessions
  • Authenticate/refresh an existing session
  • Revoke a session (Sign out)
• Biometrics
  • Register/authenticate with biometrics
• OAuth
  • Register/authenticate with native Google OneTap
  • Register/authenticate with our supported third-party OAuth providers (Amazon, BitBucket, Coinbase, Discord, Facebook, Github, GitLab, Google, LinkedIn, Microsoft, Salesforce, Slack, Twitch, or Yahoo)
• Passkeys
  • Register/authenticate with Passkeys
• User Management
  • Get or fetch the current user object (sync/cached or async options available)
  • Delete factors by id from the current user

• Magic links
  • Send/authenticate magic links via Email
  • Send/authenticate discovery magic links via Email
• Sessions
  • Authenticate/refresh an existing session
  • Revoke a session (Sign out)
• Members
  • Get or fetch the current user object (sync/cached or async options available)
• Organizations
  • Get or fetch the current user's organization
• Passwords
  • Authenticate a member by email and password
  • Check password strength
  • Reset a password
• Discovery
  • Create Organizations
  • Exchange sessions between Organizations
  • Find Organizations

The SDK provides several different mechanisms for handling the asynchronous code, so you can choose what best suits your needs.

• Coroutines
• Callbacks

If you are completely new to Stytch, prior to using the SDK you will first need to visit Stytch's homepage, sign up, and create a new project in the dashboard. You'll then need to adjust your SDK configuration — adding your app's applicationId to Authorized environments and enabling any Auth methods you wish to use.

This SDK supports Android API level 23 and above (distribution stats)

Add the Stytch dependency to your app/build.gradle file:

implementation 'com.stytch.sdk:sdk:latest'

Add the necessary manifest placeholders for our OAuth manager/receiver activities (if you are not using our Third-Party OAuth providers, you must still include this, but can leave the values blank). These values can be any valid scheme or host, and do not relate to your OAuth settings in the Stytch Dashboard. These are only used internally within your app to register a receiver activity. More information is available in the Consumer OAuth documentation.

android {
    defaultConfig {
        manifestPlaceholders = [
            'stytchOAuthRedirectScheme': '[YOUR_AUTH_SCHEME]', // eg: 'app'
            'stytchOAuthRedirectHost': '[YOUR_AUTH_HOST]', // eg: 'myhost'
        ]
    }
}

1. Go to https://stytch.com/dashboard, and sign up/log in with your email address.

2. Once you are on the dashboard, click on the "API Keys" tab on the left. Scroll down to the "Public tokens" section and copy your public token.

3. In your android app, before you call any other part of the Stytch SDK, you must first call the configure function and pass in your applicationContext and public token:

import com.stytch.sdk.consumer.StytchClient

StytchClient.configure(
    context = application.applicationContext,
    publicToken = BuildConfig.STYTCH_PUBLIC_TOKEN
)

import com.stytch.sdk.b2b.StytchB2BClient

StytchB2BClient.configure(
    context = application.applicationContext,
    publicToken = BuildConfig.STYTCH_PUBLIC_TOKEN
)

This example shows a hypothetical Android files, with deeplink/universal link handling.

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)

    // omitted

    if (intent.action == Intent.ACTION_VIEW) {
        handleIntent(intent)
    }
}

private fun handleIntent(intent: Intent) {
    intent.data?.let { appLinkData ->
        viewModel.handleUri(appLinkData)
    }
}

import com.stytch.sdk.common.StytchResult
import com.stytch.sdk.common.network.responseData.BasicData
import com.stytch.sdk.consumer.StytchClient

lateinit var result: StytchResult<BasicData>

fun handleUri(uri: Uri) {
    viewModelScope.launch {
        result = StytchClient.handle(uri = uri, sessionDurationMinutes = 60u)
    }
}

<activity android:name="com.stytch.exampleapp.MainActivity"
          android:exported="true">
    <!--omitted-->
    <intent-filter android:label="@string/deep_link_title">
        <action android:name="android.intent.action.VIEW"/>
        <category android:name="android.intent.category.DEFAULT"/>
        <category android:name="android.intent.category.BROWSABLE"/>
        <data
            android:scheme="app"
            android:host="@string/host"
            android:pathPrefix="/"/>
    </intent-filter>
</activity>

With the above in place your app should be ready to accept deeplinks

The above code is used in practice in the Example Apps, which can be run and used to test out various flows of the SDK. In order to run the application, you have to define some gradle properties in your global or local gradle.properties.

• STYTCH_PUBLIC_TOKEN - This token can be retrieved from your Stytch dashboard as mentioned before in this README.
• GOOGLE_OAUTH_CLIENT_ID - This client ID is configured in your Google OAuth settings. You can leave it blank if you are not testing Google OneTap

• STYTCH_B2B_PUBLIC_TOKEN - This token can be retrieved from your Stytch dashboard as mentioned before in this README.
• STYTCH_B2B_ORG_ID - You must create an organization in your Stytch product, and retrieve this ID

As seen in What can I do with the Stytch SDK?, there are a number of different authentication products available. Here, we'll showcase a simple example of using the OTP product.

This example shows a hypothetical function you could use to use SMS authentication in your app, delegating much of the work to the StytchClient under the hood.

import com.stytch.sdk.common.StytchResult
import com.stytch.sdk.common.network.responseData.BasicData
import com.stytch.sdk.consumer.StytchClient

lateinit var result: StytchResult<BasicData>

fun loginOrCreateSMS() {
    if (phoneNumberIsValid) {
        viewModelScope.launch {
            result = StytchClient.otps.sms.loginOrCreate(OTP.SmsOTP.Parameters(phoneNumberTextState.text))
        }
    } else {
        showPhoneError = true
    }
}

Additional documentation is available for the consumer and B2B SDKs within this repository.

Full reference documentation is available here.

Q.How does the SDK compare to the API?

A.The SDK, for the most part, mirrors the API directly — though it provides a more opinionated take on interacting with these methods; managing local state on your behalf and introducing some defaults (viewable in the corresponding init/function reference docs). A primary benefit of using the SDK is that you can interact with Stytch directly from the client, without relaying calls through your backend.

Q. What are the some of the default behaviors of the SDK?

A. A few things here: 1) the session token/JWT will be stored in/retrieved from the system encrypted storage, so will safely persist across app launches. 2) The session and user objects are not cached by the SDK, these must be pulled from the authenticate responses and stored by the application. 3) After a successful authentication call, the SDK will begin polling in the background to refresh the session and its corresponding JWT, to ensure the JWT is always valid (the JWT expires every 5 minutes, regardless of the session expiration.)

Q. Are there guides or sample apps available to see this in use?

A. Yes! There is a Demo App included in this repo, available here (consumer application) and here (B2B application).

Feel free to reach out any time at support@stytch.com, our Slack, or our Forum.

The Stytch Android SDK is released under the MIT license. See LICENSE for details.