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

Mobile Web SDK

PreviousAndroid OAuth SDKNextNumber Verification Plugin

Last updated 5 years ago

Was this helpful?

“Mobile Web SDK is currently supported only for browsers running on Android OS”

How does Truecaller SDK work for mobile websites and interfaces ?

Please refer .

Where can I find the technical documentation for integration on my mobile web app / PWA ?

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 .

How much time does it take for Truecaller to send the access token callback once a user approves the verification request ?

  • As soon as a user clicks ‘Continue’ on the Truecaller profile dialog, our backend makes a POST request to the callback URL configured by you while creating the app from your developer account

  • In case users deny sharing their information, we immediately send you an error response on the same callback URL

  • The entire process normally takes a few milliseconds

What should I do once I receive user’s access token on my callback endpoint ?

Please refer

I am unable to add the callback URL to my developer account

The callback URL you add has to be an ‘https’ endpoint, and you won’t be able to add an ‘http’ endpoint. Please ensure that you have SSL setup before adding the callback URL For guidelines on properly setting up your callback URL, please refer .

What is request ID parameter in the deep link schema ?

Request ID corresponds to a unique identifier that you can set from your end while initiating any verification request. Once users give their consent for sharing the profile information with your mobile web app, we share the same request ID to you along with the access token on your callback URL. This can be used as a request correlation for mapping.

The request ID parameter needs to be a URL safe string with a length of minimum 8 characters and a maximum of 64 characters

here
here
here
here
here