1. Quickstart
CallerAPI Documentation
  • Quickstart
  • Use cases
    • For carriers (MNOs/MVNOs)
    • CPaaS platforms
    • Cloud communications providers
    • SIP trunking providers
    • PBX/Cloud PBX
    • UCaaS vendors
  • Account
    • Balance and email
      GET
  • Spam protection
    • Daily spam reports
      • Webhook
        • Subscribe to daily reports
        • Unsubscribe from daily reports
        • List webhook subscriptions
        • Manual dispatch of reports
        • Test webhook
      • REST
        • Fetch daily spam reports
    • Spam score + HLR
      GET
    • 15 days spam CSV snapshot
      GET
  • Mobile SDK
    • Get started
    • Quickstart
      • What you get
      • Get your keys
      • Android
      • iOS
      • Flutter
      • React Native
      • Check it works
    • Call screening
      • What each platform can do
      • Android
  • Data partners
    • Partner tems & docs
    • Upload spam reports
      POST
    • Upload contacts
      POST
  • Fraud prevention
    • Ported date
    • Porting history
    • Online presence
    • KYC user identity
  • Schemas
    • Spam protection
      • Spam score request
      • Business info
      • Carrier info
      • Complaint (without number)
      • Daily spam reports request
      • Complaint (with phone)
  1. Quickstart

Get your keys

You need three values. This page shows you exactly where to click. It takes about two minutes.

Step 1: open the setup page#

Go to https://callerapi.com/dashboard/sdk-setup.
If you are not signed in, the site sends you to Google sign-in first. Sign in and the setup page opens.

Step 2: create an app#

Find the card named Your apps. Click New app.
FireShot Capture 004 - Set up the SDK - CallerAPI - callerapi.com.png
A small box asks for a name. Type anything you recognize later, for example My app, debug. Click OK.
Screenshot 2026-07-29 at 20.32.44.png
Create one app per real app you ship. Do not reuse one app for your iOS and Android builds, because the dashboard reports usage per app.

Step 3: copy the three credentials#

The page now shows your credentials. Copy all three.
Screenshot 2026-07-29 at 20.33.47.png
CredentialWhat it is forKeep it secret?
client_keyCounts your monthly devices for billingNo, it ships inside your app
sdk_keyNames your app to the lookup serviceNo, it ships inside your app
sdk_secretSigns your app's requestsYes, treat it as a password
The SDK secret is shown once. Copy it now and store it in your password manager. If you lose it, create a new app.

Step 4: keep them out of your git history#

All three values end up inside your app binary, so a determined person can read them out of a shipped app. That is expected, and the server limits the damage. It checks every request against the app the credentials were issued to, so a credential copied into a different app stops working.
Committing them to a public repository is still a bad idea. Anyone who finds them can spend your quota until you notice.
Read them from your build configuration instead:
Android: put them in local.properties or an environment variable, then inject them into the manifest with manifestPlaceholders.
iOS: put them in an .xcconfig file that git ignores.
Flutter and React Native: same as above, in the native folders.
Each platform page shows the plain version first, so you can get a lookup working. Move to the build configuration before you ship.

What "sandbox" means on this page#

Your new app says sandbox. Sandbox is free, and lookups return real data. The only limit is 200 devices in a calendar month.
Screenshot 2026-07-29 at 20.27.50.png

Next#

Add the SDK to your app: Android, iOS, Flutter, or React Native.
Modified at 2026-07-29 20:10:28
Previous
What you get
Next
Android
Built with