Sinch Developer Documentation

Building blocks to enable rich customer communication

Android phone number verification set up

Set up phone number verification in Android for the first time with the Sinch Verification SDK.

This guide will show you how to set up the Sinch Verification SDK for the first time.

Register an Application

  1. Register a Sinch Developer account
  2. Set up a new Application using the Dashboard, where you can then obtain an Application Key.
  3. Enable Verification for the application by selecting: Authentication > Public under App > Settings > Verification

Add the Sinch library

The Sinch Verification SDK is available publicly on jCenter. To include it in your Android application, make sure your project level build.gradle file contains:

buildscript {
    repositories {
        google()
        jcenter()
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

Now, in your module level build.gradle file, you can add Sinch SDK as a dependency:

dependencies {
    implementation 'com.sinch.android.sdk.verification:verification-all:*.*.*'
  }

If your application uses all the verification methods it's easiest to add the verification-all package. If you intend to use only specific verification types, you may include only their dependencies.

  • verification-sms
  • verification-flashcall
  • verification-callout
  • verification-seamless
Example:

If your application relies only on SMS verification and doesn't use any other verificaiton methods you should simply add:

dependencies {
    implementation 'com.sinch.android.sdk.verification:verification-sms:*.*.*'
  }

The latest version of the SDK can be checked on Bintray.

Samples

A repository with fully functional samples is available on GitHub.

Edit on GitHub

Updated 13 days ago



Android phone number verification set up


Set up phone number verification in Android for the first time with the Sinch Verification SDK.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.