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

Developer Account

PreviousGeneralNextAndroid App SDK

Last updated 5 years ago

Was this helpful?

How can I access my Truecaller developer account ?

  • You can create your Truecaller developer account by signing up here :

  • If you already have a Truecaller developer account, you can simply login to your account here :

What can I do with my Truecaller developer account ?

Once you setup your Truecaller developer account you can:

  • create new applications and get respective app keys for using Truecaller SDK

  • edit an existing app

  • reset your account password

How can I add an app in my account ?

  • For Android apps, you need a valid app name, package name, SHA1 fingerprint and Google app hash code ( optional ) for your app build

  • For iOS apps, you need a valid app name, bundle Id and a teamId

  • For mobile web apps, you need a valid name, public url [ domain name ] for the web app and a publicly accessible callback URL [ an endpoint on your server where Truecaller’s server will post a user’s access token once they give consent to share their Truecaller profile with your app ]

Things that I need to keep in mind -

While creating a new app, you cannot have :

  • more than one active android app with the same combination of package name and SHA1 fingerprint

  • more than one active iOS app with the same bundle Id and teamId

  • more than one active mobile web app with the same public url and callback URL

  • If you want a new key for the same combination of params, you will need to deactivate the existing app first and then create a new one with the same identifiers

While editing an already existing app, you can only edit the following :

  • App name in case of android / iOS apps

  • Callback URL in case of web apps [ Please note that once you change the callback URL, it might take up to 30 minutes for the caching to clear out and reflect in our systems ]

You will not be able to edit main identifiers of apps such as package name, fingerprint, bundleId, teamId In case you need to have an app with the same package name but a different fingerprint, you should create a new app. You can also activate and deactivate your application. You cannot activate an application with identifiers that are already used by any of your existing apps.

I have more than one developer account. I wish to have only one account through which I should be able to manage all my apps

  • your existing account's email id

  • existing app details

  • email id of the new account which you wish to continue using

We will make sure we map your existing apps to the single account you wish to use.

If you have more than one account and wish to use only one, please contact us by sending :

https://developer.truecaller.com/sign-up
https://developer.truecaller.com/login
here