Truecaller SDK
  • Hello!
  • Why Truecaller SDK
  • Getting Started
  • ANDROID
    • 🆕OAuth SDK 3.0
      • Implementing user flow for your App
      • Scenarios for all user verifications : Truecaller and Non Truecaller Users
      • Integration Steps
        • Generating Client ID
        • Setup
        • Implementing Callbacks
        • Initialisation
        • Setting up OAuth parameters
        • Invocation
        • Customisation
        • Clearing SDK Instance
        • Handling Error Scenarios
        • Integrating with your Backend
          • Fetching User Token
          • Fetching User Profile
        • Non Truecaller User Verification
          • Completing Verification
          • TrueException
          • Server Side Validation
      • Instrumentation
      • Getting Release Ready
        • Testing your verification flow
          • Non-Truecaller user verification flow
          • Truecaller user verification flow
          • Test Setup
        • Google play store app permission declaration form
        • Moving to Production
    • SDK v2.8.0
      • Implementing user flow for your app
      • Scenarios for all user verifications : Truecaller and Non Truecaller Users
      • Generating App Key
      • Integrating with your App
        • Setup
        • App Key Configuration
        • Initialisation
        • Customisation
        • Implement Callbacks
        • Clearing SDK instance
        • Handling Error Scenarios
        • Verifying non Truecaller users
          • TrueException
          • Completing Verification
        • Advanced Steps
      • Server Side Response Validation
        • For Truecaller users verification flow
        • For Non-Truecaller users verification flow
      • Instrumentation
      • Getting Release Ready
        • Testing your verification flow
          • Truecaller user verification flow
          • Non-Truecaller User Verification Flow
          • Test Setup
        • Google Play App Signing
        • Google Play Store app permissions declaration
        • Google Play Policy Change for Device Identifiers
      • Changelog
  • MOBILE WEBSITES
    • Implementing user flow for your Mobile Website
    • Generating App Key
    • Integrating with your mobile website
      • Initialisation
      • Invoking verification
      • Fetch User Profile
      • Completing User Verification
      • Handling Error Scenarios
    • Getting Release Ready
      • Instrumentation
      • Testing your verification flow
  • IOS
    • Generating App Key
    • Integrating with your iOS App
      • Setup
      • Configuration
      • Usage
        • Swift
        • Objective-C
      • Verifying Non-Truecaller app users
        • Completing Verification
      • Handling Error Scenarios
        • Safari Redirection
    • Server Side Response Validation
  • SHOPIFY APP
    • Generating App Key
    • App Configuration
    • Deactivating App Block
  • FAQs
    • General
    • Developer Account
    • Android App SDK
    • Android OAuth SDK
    • Mobile Web SDK
    • Number Verification Plugin
  • PRODUCT UPDATES
    • App Review Process
    • Introducing dark theme
Powered by GitBook
On this page

Was this helpful?

  1. FAQs

Android App SDK

PreviousDeveloper AccountNextAndroid OAuth SDK

Last updated 4 years ago

Was this helpful?

How does Truecaller SDK work for android apps ?

Please refer for details.

Can I use Truecaller SDK to verify mobile numbers for all my app users globally ?

Truecaller SDK v2.0 has 2 key functionalities.

  • With the 1-tap verification functionality, you can verify mobile number of any active Truecaller app user (globally) on your app

  • With the missed call based functionality, you can verify mobile number of any user who may not be an active Truecaller app user. The missed call functionality is currently available for India market and on android platform only

Where can I find the technical documentation for integration on my android app ?

Please refer to the technical documentation .

What is the right way / How do I implement the user flow in my app using Truecaller SDK ?

Please refer for details.

Why do I get "Partner Unauthorised [ ERROR_TYPE : 3 ] " error ?

One app key can be used only for a particular combination of package name and SHA1. Different partner key needs to be used for any different combination of the two parameters.

You might be getting this error because you're either:

  • using a wrong app key

  • using the right key with either or both wrong package name and fingerprint

For details on generating and managing app keys for different app builds. Please refer .

How can I find the SHA1 of my android app build ?

What is the TruecallerSDK.getInstance().isUsable() method used for ?

The isUsable() method, helps you check if the Truecaller SDK can be used for user verification or not. Depending on the "sdkOptions" scope you have defined while initialising the Truecaller SDK ( WITH_OTP or WITHOUT_OTP ), below are the expected results :

WITH_OTP : In this case, Truecaller SDK can be used to verify existing Truecaller users as well as non-Truecaller app users ( via missed call/ OTP flow ), hence isUsable() method would always return "true".

WITHOUT_OTP : In this case, Truecaller SDK can be used to verify only existing Truecaller users, hence isUsable() method would return "true" only if the users have Truecaller SDK on their devices. It would return false otherwise

How do I verify the authenticity of Truecaller SDK response ?

Does Truecaller SDK need any app permission ?

For the verification of existing Truecaller users who have the app present on their smartphones, the SDK does not require any android system permissions, whatsoever

How can I test my application with Truecaller SDK integration to make it release ready ?

Do I need to submit an app permissions declaration form while uploading my app on google play store ?

Please refer for details.

Please refer .

For the automatic verification of users who don't have the Truecaller app on their devices, the SDK can facilitate the verification by sending a drop call in background / fallback SMS based OTP. If you choose to use this service for the verification of non-Truecaller users as well, the SDK will require you to ask for READ_CALL_LOG and READ_PHONE_STATE permissions. You can read more about the usage of these permissions

For details on test scenarios and setup, please refer

If you are also using the missed call based non Truecaller user verification functionality of the SDK ( currently supported for India only ), you need specific phone permissions as described . For submitting your application on Google play store, please refer to our recommended guidelines

here
here
here
here
here
here
here
here
here
here